-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
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
Allow specifying a default filter for a profile #847
Comments
Hi, thanks for the question! I agree that this would be good. The main challenge here is presenting this in the UI -- we need to make it clear that it's not nextest's fault that only a subset of tests is being run. |
This is now supported via the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have some integration tests that require a backing data store to be available. By default, I'd like only the "unit" tests to run, but I'd like this to be something that any other user can do by just specifying
cargo nextest run
, rather thancargo nextest run -E 'not (kind(test) and binary(integration))'
. I think that adding a property into the profile configuration would be great. This would then also enable "named" filters in a way, through the use of the profiles feature.The text was updated successfully, but these errors were encountered: