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
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 runs cargo nextest run if available, but falls back to regular cargo 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:
svix-jplatte
changed the title
Add support for cargo tests --skip and --exact command line flags
Add support for cargo tests --skip and --exact command line flags
May 6, 2024
Just like the existing support, filter expressions must be ANDed with them. i.e. if both a filter expression and --skip/--exact is passed in, both should be matched for a test to be run.
I'm not exactly sure of the semantics of --skip and --exact especially when they're passed in together, so a full description of the semantics, with tests would be wonderful.
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: