You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all of the data associated with tests is embedded in the binary. But if a user wanted to explore the set of test cases, they have to go look at the source code in a git repository.
Ideally, the test runner's command-line interface would provide a way to list test cases, including filtering test cases against one or more patterns, and to show test case and test suite details.
The text was updated successfully, but these errors were encountered:
I would find this very useful, and it would alleviate #887. A simple solution could be to print all test names after the line Filtered tests to 123 test case permutation(s) with the --vv flag. That's not very discoverable, but maybe it's good enough to document it in configuring_and_running_tests.md and in the flag description.
Currently, all of the data associated with tests is embedded in the binary. But if a user wanted to explore the set of test cases, they have to go look at the source code in a git repository.
Ideally, the test runner's command-line interface would provide a way to list test cases, including filtering test cases against one or more patterns, and to show test case and test suite details.
The text was updated successfully, but these errors were encountered: