Enable test query for exact test name #1900
Merged
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.
The standard way of running a specific test is by using a query. E.g. to test
test_codecs
However, this matches tests by substring, so for more popular test names the query may catch several tests. The example above selects the following tests for running:
Even running more specific
will still match two tests.
To be able to run just one selected test, one must resolve to construct an elaborate query, which is also framework specific:
This PR adds the possbilility to query for the exact test name and reduce the verbosity of the query filter. The above test can be now filtered out and run on all supported frameworks concurrently by:
This is btw an excellent way to check is a given test is parallel-safe.
The old behaviour for queries that start with
CPython
orIronPython
(matching by substring) can still be achieved by adding explicitName~
to the query, e.g.