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
Currently, test name filters can be specified both with and without --:
cargo nextest run my_test # ... (format 1)
cargo nextest run -- my_test # ... (format 2)
This proposal makes it so that format 1 is deprecated and eventually disabled, and format 2 is the only format supported.
I'd also like to make this a test case for rolling out behavior changes.
Motivation
Originally, nextest only supported test name filters in format 1. Support for format 2 was added in #265 soon after nextest's initial public release.
So far we've emphasized format 1 in documentation, but we've found that this format can cause strange issues in practice like #1108, and third-party integrations like cargo llvm-cov nextest (specifying cargo llvm-cov nextest run will cause no tests to be run).
Timeline
2023-11-14: Emphasize format 2 on website and in help text. Hide format 1 from cargo nextest run --help.
Early 2024: Produce a warning in the CLI if format 1 is used.
April 2024, 3 months after step 2: Error out if format 1 is used.
Summary
Currently, test name filters can be specified both with and without
--:This proposal makes it so that format 1 is deprecated and eventually disabled, and format 2 is the only format supported.
I'd also like to make this a test case for rolling out behavior changes.
Motivation
Originally, nextest only supported test name filters in format 1. Support for format 2 was added in #265 soon after nextest's initial public release.
So far we've emphasized format 1 in documentation, but we've found that this format can cause strange issues in practice like #1108, and third-party integrations like
cargo llvm-cov nextest(specifyingcargo llvm-cov nextest runwill cause no tests to be run).Timeline
cargo nextest run --help.