nextest-filtering 0.21.1

Fixed

• Filterset expressions like not(test(foo)), all()and(test(foo)), and all()or(test(foo)), where not, and, or or is immediately followed by an opening parenthesis, now parse correctly. Previously, a separating space was required. (#3367)

cargo-nextest 0.9.137

Changed

• CLI --help descriptions, configuration-reference docs, and JSON schema descriptions now use consistent language and voice. (#3366)

Fixed

• Filterset expressions like not(test(foo)), all()and(test(foo)), and all()or(test(foo)), where not, and, or or is immediately followed by an opening parenthesis, now parse correctly. Previously, a separating space was required. (#3367)

nextest-runner 0.117.0

nextest-runner-0.117.0

[nextest-runner] version 0.117.0

cargo-nextest 0.9.136

Added

• Following up from the recently-added schema for repository configuration, nextest now also provides a JSON Schema for user configuration. The schema for the running version can be obtained by running cargo nextest self schema user-config. (#3351)

Changed

• The max-progress-running user-config setting no longer accepts numeric strings like "8" (an undocumented fallback). The supported values remain a non-negative integer (e.g. 8) or "infinite". (#3350)

nextest-runner 0.116.0

nextest-runner-0.116.0

[nextest-runner] version 0.116.0

nextest-runner 0.115.0

nextest-runner-0.115.0

[nextest-runner] version 0.115.0

cargo-nextest 0.9.135

Fixed an issue with a from-crates.io build.

cargo-nextest 0.9.134

Added

• Nextest now provides a JSON Schema for repository configuration at .config/nextest.toml, enabling validation and IDE autocompletion via the Tombi language server.

  Thanks ya7010 for your first contribution, and for maintaining Tombi!

  (Note that the Taplo language server is not supported due to a crash bug. The schema has been tested to work with Tombi.)

• For target triples that nextest doesn't have built-in information about, nextest now invokes rustc --print=cfg --target=<triple> to resolve platform information before falling back to heuristic detection. This is particularly useful for custom builds of the Rust toolchain. (#3331)

  Thanks mhatzl for your first contribution!

Changed

• User config platform overrides are now always evaluated against the build target: the platform nextest was compiled for. Previously, the build target was used in some cases and the host platform in others. (#3285)

  In most cases the build target matches the host platform, but they can differ when, for example, running an x86_64-unknown-linux-musl nextest binary on a glibc (-gnu) host. This change does not affect per-test overrides, which continue to be matched against the host or target platform of the tests being run.

Fixed

• cargo nextest store export and cargo nextest store export-chrome-trace now verify the store format version before exporting, matching the behavior of cargo nextest replay and the rerun commands. (#3287)

nextest-runner 0.114.0

nextest-runner-0.114.0

[nextest-runner] version 0.114.0

nextest-metadata 0.14.1

Added

• A new GLOBAL_TEST_GROUP constant ("@global"), representing the implicit global test group that all tests belong to unless assigned to a custom group.