nextest-runner 0.68.0

See the changelog for cargo-nextest 0.9.85.

cargo-nextest 0.9.85-rc.2

Changed

When no tests are run, the default behavior now is to exit with code 4
(NO_TESTS_RUN). This is a behavior change, as documented in #1646.

Added

SHA-256 and BLAKE2 checksum files are now published for each release.

cargo-nextest 0.9.85-rc.1

Changed

When no tests are run, the default behavior now is to exit with code 4
(NO_TESTS_RUN). This is a behavior change, as documented in #1646.

Added

SHA-256 and BLAKE2 checksum files are now published for each release.

nextest-runner 0.67.0

See the changelog for cargo-nextest 0.9.84.

nextest-runner 0.66.0

See the changelog for cargo-nextest 0.9.83.

cargo-nextest 0.9.84

Fixed

• Fixed a rare crash during test run cancellation (#1876).

cargo-nextest 0.9.83

Added

• Per-platform default filters are now supported via overrides. For example, to
  skip over tests with the substring unix_tests by default on Windows, add
  this to .config/nextest.toml:

  [[profile.default.overrides]]
  platform = "cfg(windows)"
  default-filter = "not test(unix_tests)"

• cargo nextest run --build-jobs now accepts negative numbers as arguments,
  similar to other commands like cargo nextest run --test-threads and cargo build. Negative numbers mean "use all available cores except for this many".

  Thanks to mattsse for your first contribution!

Internal improvements

• Internal targets updated to Rust 1.82.
• Runner logic refactored to handle upcoming features.

nextest-runner 0.65.0

See the changelog for cargo-nextest 0.9.82.

cargo-nextest 0.9.82

Added

• For crates with a build script, nextest now reads their output and sets environment variables from
  within them for tests. This matches cargo test's behavior. However, note that this usage is
  discouraged by Cargo.

  Thanks to chrjabs for your first contribution!

• On Unix platforms, nextest now also intercepts the SIGQUIT signal, in addition to the existing
  SIGINT, SIGTERM, etc. More signals will be added to this list as makes sense.

Internal improvements

• Switch internal logging over to the fantastic tracing library. Nextest doesn't do much
  structured logging or event/span logging yet, but tracing provides a great foundation to add that
  in the future.
• Internal dependency updates.

nextest-runner 0.64.0

See the changelog for cargo-nextest 0.9.81.