Use unittest2 test runner #3073
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
Since upgrading to unittest2, the test runner prints the command line to re-run a failed test - this however relies on actually using the unittest2 command line runner. Previously, test files were assigned numbers - with the unittest2 runner, tests are run using suite/category names instead, like so: ``` # run the Genesis suite build/all_tests "Genesis::`` # run all tests with "blsMapG1" in the name build/all_tests "blsMapG1*" # run tests verbosely build/all_tests -v ``` A reasonable follow-up here would be to review the suite names to make them easier to run :)
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.
Since upgrading to unittest2, the test runner prints the command line to re-run a failed test - this however relies on actually using the unittest2 command line runner.
Previously, test files were assigned numbers - with the unittest2 runner, tests are run using suite/category names instead, like so:
A reasonable follow-up here would be to review the suite names to make them easier to run :)