Use Smoke instead of shelltestrunner #1710
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
paulcadman
reviewed
Jan 9, 2023
paulcadman
reviewed
Jan 9, 2023
paulcadman
reviewed
Jan 9, 2023
paulcadman
reviewed
Jan 10, 2023
paulcadman
approved these changes
Jan 10, 2023
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.
This PR adds smoke tests using Smoke tool for all the shell tests we have. One reason for adopting Smoke instead of the previous tool,
shelltestrunner, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax.To add a new smoke test, create a file with the suffix ".smoke.yaml" in the
tests/smokefolder. In such a folder, you can also find examples of how to test the CLI.