-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Add support for cargo test
s --skip and --exact command line flags
#1483
Comments
cargo tests
--skip and --exact command line flagscargo test
s --skip and --exact command line flags
Hi -- I was hesitant to add this at first, but over the last few months I've changed my mind. I'm happy to accept a PR for this. Some notes:
|
I was able to get it to work, see #1653. It's in draft state though because I broke a test and couldn't really figure out how to add a new one either. And it's quite likely I didn't solve it in the best possible way. |
Released as part of cargo-nextest 0.9.80, which will be out within the next 15-20 minutes. Thanks again for your hard work! |
Also added documentation: https://nexte.st/docs/running/#--skip-and---exact |
Thanks! |
Hi, I was just looking for an issue about
--skip
in nextest and found #29 which is saying that these are supported, but using different syntax. This is problematic for my use case since I have a test script that runscargo nextest run
if available, but falls back to regularcargo test
if nextest is not installed. I also think that for interactive usage,--skip
and--exact
are much easier to use than the filter expression syntax.Would you consider adding support for these flags? The implementation could just instantiate the appropriate filter expressions internally, so it should be really simple.
The text was updated successfully, but these errors were encountered: