cargo-nextest 0.9.86-b.3

Since beta 2:

Added

• Added a way to pass in extra arguments to the test binary at runtime, via
  run-extra-args. See Passing in extra arguments.

Fixed

• When adding extra files to an archive, nextest now ignores empty and .
  path components in the specification while joining the specified path. This
  means that archives won't accidentally get duplicated entries.
• Update idna to address RUSTSEC-2024-0421. Since nextest only accesses
  domains that do not use punycode, we disable that support entirely.

nextest-runner 0.69.0-b.2

See the changelog for cargo-nextest 0.9.86-b.2.

cargo-nextest 0.9.86-b.2

Since beta 1:

• Fixed --no-fail-fast and --fail-fast not being honored properly.
• Internal refactoring work, with no expected functional changes.

nextest-runner 0.69.0-b.1

See the changelog for cargo-nextest 0.9.86-b.1.

cargo-nextest 0.9.86-b.1

This release of nextest has a number of internal and external improvements. Please try it out
and report issues you find!

Added

Interactive test state querying

Test state can now be queried interactively, via any of the following means:

• Typing in t in an interactive terminal.
• Pressing Ctrl-T, on macOS and other BSD-based platforms where the SIGINFO signal
  is available and recognized by the terminal driver. (SIGINFO will be supported on
  illumos once an upstream Tokio issue is fixed.)
• On Unix platforms, sending the nextest process the SIGUSR1 signal.

This command shows a list of all tests currently running, along with their
status, how long they've been running, and currently-captured standard output
and standard error.

Processing the t key requires alterations to the terminal, which may lead to
issues in rare circumstances. To disable input key handling, pass in
--no-input-handler.

--max-fail runner option

The new --max-fail option allows you to specify the maximum number of test
failures before nextest stops running tests. This is an extension of the
existing --fail-fast and --no-fail-fast options, and is meant to allow users
to strike a balance between running all tests and stopping early.

• --fail-fast is equivalent to --max-fail=1.
• --no-fail-fast is equivalent to --max-fail=all.

Configuration for --max-fail will be added in a future release (#1944).

Thanks to AJamesyD for your first contribution!

Fixed

Nextest now supports being run in Cargo setups where the Cargo.toml that
defines the workspace is not hierarchically above the workspace members. This is
an uncommon setup, but it is supported by Cargo--and now by nextest as well.

Thanks to PegasusPlusUS for your first
contribution!

Changed

• The progress bar and other UI elements use Unicode characters if available.
• Some more minor improvements that should lead to a more cohesive user experience.
• MSRV for compiling nextest is now Rust 1.81.

cargo-nextest 0.9.85

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.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.