Tracking issue for filter expressions

[sunshowers]

Documentation: https://nexte.st/book/filter-expressions.html

TODO:

• Add partition operator to filter expressions? #159
• Basic test name filters and filter expressions should be ORed #160
• Add help text explaining that --skip and --exact are covered by filter expressions #29

cc @Guiguiprim

[pan93412]

I have such the tests:

crypto-markets::bitmex aaaaa
crypto-markets::bitmex bbbbb
crypto-markets::bitmex ccccc
crypto-markets::others bbbbb
crypto-markets::dont_exclude aaaaa

How can I exclude the bitmex tests while still including others and dont_exclude? I tried all() - package(/bitmex/) (and package(~bitmex)), and it reported:

$ cargo nextest run -E 'all() - package(/bitmex/)'

  error: operator didn't match any packages
   ╭────
 1 │ package(/bitmex/)
   ·         ────┬───
   ·             ╰── no packages matched this
   ╰────

error: failed to parse filter expression

While all() - test(/bitmex/) (test(bitmex), test(~bitmex)) can only match:

crypto-markets::bitmex bitmex_aaaaa
crypto-markets::bitmex bitmex_bbbbb
crypto-markets::bitmex bitmex_ccccc
crypto-markets::others bitmex_bbbbb
crypto-markets::dont_exclude bitmex_aaaaa

[sunshowers]

Thanks for pointing this out! You're right that this is a gap right now. The next version of nextest (hopefully done in a couple of days) will add a new binary predicate for this purpose. If you build nextest from main you can try it out right now.

[sunshowers]

Filter expressions have been released as part of cargo-nextest 0.9.25.