We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I feel we had this at some point but haven't been able to find it ....
Would be great to enable to run tests matching a specific naming pattern and/or choice or test tags expressions.
maybe shift+R queries you for naming pattern and tags expression (preferably with some kind of history of past used expressions):
shift+R
name pattern: org.acme.test.db.* tags expression: no-io
would run tests in org.acme.test.db.* packages and only those with tag no-io or
org.acme.test.db.*
no-io
name pattern: *System* tags expression:
will run test with System in name ignoring any tags.
The text was updated successfully, but these errors were encountered:
idea is to have it be a persistent "filter" to be able to run again and again instead of full / automatic selected test suite
Sorry, something went wrong.
@stuartwdouglas reminded me about https://quarkus.io/guides/continuous-testing#quarkus-test-dev-testing-test-config_quarkus.test.include-tags
turns out possible to set via "test" command - but test --help is broken so hard to discover.
test --help
test tests
No branches or pull requests
Description
I feel we had this at some point but haven't been able to find it ....
Would be great to enable to run tests matching a specific naming pattern and/or choice or test tags expressions.
Implementation ideas
maybe
shift+R
queries you for naming pattern and tags expression (preferably with some kind of history of past used expressions):would run tests in
org.acme.test.db.*
packages and only those with tagno-io
or
will run test with System in name ignoring any tags.
The text was updated successfully, but these errors were encountered: