Test some important legacy CLI commands #211
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pjcdawkins
changed the title
pjcdawkins
force-pushed
the
test-legacy-cli-commands
branch
from
4a6689e to
15e3950
Compare
pjcdawkins
force-pushed
the
test-legacy-cli-commands
branch
from
15e3950 to
70793c5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Targeting #210
This adds tests targeting a few important legacy CLI commands (detailed in commits).
Each command can have its own ad-hoc server providing enough responses so that the command produces useful output.
If/when the number of tests expands this could be refactored in many ways.
Ideally this should run in GitHub but it's in GitLab (where the build works) for now.