Skip to content

Changelog

This page documents new features and bugfixes for cargo-nextest. Please see the stability policy for how versioning works with cargo-nextest.

0.9.108 - 2025-10-21

Added

  • In CI, test status lines now include a counter showing the number of tests that have been executed (#2618). Thanks bobrik for your first contribution!

Changed

  • For leaky tests, default leak timeout increased from 100ms to 200ms.
  • MSRV for building nextest updated to Rust 1.87.

0.9.107 - 2025-10-21

This version was not published due to a build issue.

0.9.106 - 2025-10-13

Fixed

Changed

  • Update builtin list of targets to Rust 1.90.

0.9.105 - 2025-10-02

Changed

On Windows, job objects are now created with JOB_OBJECT_LIMIT_BREAKAWAY_OK. This enables test processes to have their children be assigned a different job object, which is particularly relevant on Windows 7 since that platform doesn't have nested job objects.

Thanks to Guiguiprim for the contribution!

0.9.104 - 2025-09-14

Added

  • For stress tests, summary lines now indicate the number of iterations passed and/or failed.

Changed

  • Always forward --config arguments to Cargo invocations. Thanks to benschulz for your first contribution!
  • Internal dependency update: target-spec updated to 3.5.1, updating built-in targets to Rust 1.89.

0.9.103 - 2025-08-24

Added

  • Initial support for stress tests: running tests a large number of times in a loop.

Changed

  • The libtest-json-plus output now produces test results immediately rather than at the end of the run. This is allowed by the fact that with the libtest-json-plus output, it is possible to distinguish between different test binaries based on the additional nextest property.

    Thanks to dnbln for your first contribution!

Fixed

  • The heuristic detection for panicked at in tests now handles the new output format in Rust nightlies (Rust 1.91 and above): on Unix platforms, the thread ID is now also included.

    Thanks again to dnbln for fixing this.

0.9.102 - 2025-08-03

Added

  • Windows releases are now digitally signed. Thanks to the SignPath Foundation for signing nextest's Windows builds.

Known issues

  • Nextest's test suite can nondeterministically hang on machines with a large number of cores. This is a bug in Cargo 1.88, and is fixed in Cargo 1.89. See #2463 for more information.

0.9.101 - 2025-07-11

Fixed

  • Restored compatibility with Cargo's unstable bindeps feature in some circumstances.

Changed

  • Tokio downgraded to 1.45.0 to try and get to the bottom of hangs in some configurations. If you encounter nextest 0.9.100 or 0.9.101 getting stuck, please comment in #2463. Thank you!
  • MSRV updated to Rust 1.86.

0.9.100 - 2025-07-07

Added

  • A new global-timeout option allows setting a global timeout for the entire run. This is an alternative to the Unix timeout command that also works on Windows.

    For more information, see Setting a global timeout.

    Thanks to robabla for your first contribution!

  • Nextest now reports progress to the terminal emulator for display in places like the task bar, similar to Cargo 1.87 and above. Terminal progress integration uses OSC 9;4, and is enabled by default in Windows Terminal, ConEmu, and WezTerm.

    To configure this, use Cargo's term.progress.term-integration option.

0.9.99 - 2025-06-16

Added

  • Script commands now support relative-to = "workspace-root". This has minimal impact on setup scripts since they always run relative to the workspace root, but allows wrapper scripts to be invoked more easily.

Changed

  • On remapping workspace or target directories, they're now converted to absolute ones. This should not have user-visible effects.

0.9.98 - 2025-06-06

Added

Changed

  • Setup scripts are now specified within the [scripts.setup] table, for example [scripts.setup.db-generate]. The previous [script.db-generate] configuration will continue to work for a short while.

0.9.97 - 2025-05-29

Fixed

  • Worked around a Rust type inference bug as part of a dependency update (#2370).

Changed

  • The MSRV for compiling nextest is now Rust 1.85. (The MSRV for running tests remains unchanged.)

0.9.96 - 2025-05-15

Miscellaneous

  • Pre-built binaries are now built with Rust 1.87, which is the first version to support posix_spawn-based process spawning on illumos.

0.9.95 - 2025-04-30

Added

You can now mark leaky tests as failed rather than passed. The default is still to treat them as passed. For more, see Marking leaky tests as failures.

Changed

Several display formatting improvements with a focus on visual clarity and reduced UI clutter:

  • Captured output (typically for failing tests) is now indented by 4 spaces, for easier-to-scan logs. This can be disabled with the new --no-output-indent option, or by setting NEXTEST_NO_OUTPUT_INDENT=1 in the environment.
  • If tests abort or fail through unexpected means (e.g. due to a signal), nextest now prints out a status line explaining what happened. For example, (test aborted with signal 6: SIGABRT).

Fixed

Fixed an occasional hang on Linux with libtest JSON output. For more details, see #2316.

0.9.94 - 2025-04-10

Added

Official binaries are now available for aarch64-pc-windows-msvc (Windows on ARM). Installation instructions are available at Pre-built binaries under Other platforms.

Fixed

On Unix platforms, nextest will no longer attempt to set up input handling if it isn't in the foreground process group of the controlling terminal. This addresses a hang with commands like watchexec: these commands forward standard input to nextest (so is_terminal returns true), but do not give nextest full terminal control.

There are still some reports of watchexec hangs even with this change; we'll track them down and fix bugs as necessary.

0.9.93 - 2025-03-24

Fixed

  • If cargo metadata fails, print the command that failed to execute. This works around possibly-broken Cargo installations producing no output.
  • Update ring to address GHSA-4p46-pwfr-66x6.

0.9.92 - 2025-02-24

Added

  • --nff and --ff are aliases for --no-fail-fast and --fail-fast, respectively.

Fixed

  • In filtersets, binary_id patterns that don't match any binary IDs in the workspace are now rejected. This is a small behavior change that is being treated as a bugfix to align with package, deps and rdeps behavior.

    binary_id patterns are not rejected if they match any test binaries that are in the workspace, regardless of whether they're built or not. In the future, we may add a warning for binary ID patterns only matching binaries that aren't built, but this is not an error.

0.9.91 - 2025-02-13

Added

0.9.90 - 2025-02-12

Added

  • Tests are now assigned global and group slot numbers. These numbers are non-negative integers starting from 0 that are unique for the lifetime of the test, but are reused after the test ends.

    Global and group slot numbers can be accessed via the NEXTEST_TEST_GLOBAL_SLOT and NEXTEST_TEST_GROUP_SLOT environment variables, respectively. For more, see Slot numbers.

  • Test environments now have the NEXTEST_TEST_GROUP variable set to the test group they're in, or "@global" if the test is not in any groups.

0.9.89 - 2025-02-10

Added

  • To configure fail-fast behavior, max-fail can now be specified in configuration. For example, to fail after 5 tests:

    [profile.default]
fail-fast = { max-fail = 5 }

    fail-fast = true is the same as { max-fail = 1 }, and fail-fast = false is { max-fail = "all" }.

    Thanks to Jayllyz for your first contribution!

  • Within tests and scripts, the NEXTEST_PROFILE environment variable is now always set to the current configuration profile. Previously, this would only happen if the profile was configured via NEXTEST_PROFILE, as a side effect of the environment being passed through.

Changed

  • The --max-fail and --no-tests options no longer require using an equals sign. For example, --max-fail 5 and --max-fail=5 now both work.

    This was previously done to avoid confusion between test name filters and arguments. But we believe the new --no-tests default to fail sufficiently mitigates this downside, and uniformity across options is valuable.

Fixed

  • Nextest now uses rustc -vV to obtain the host target triple, rather than using the target the cargo-nextest binary was built for. This fixes behavior for runtime cross-compatible binaries, such as -linux-musl binaries running on -linux-gnu.
  • If nextest is paused and later continued, the progress bar's time taken now excludes the amount of time nextest was paused for.
  • Update rust-openssl for CVE-2025-24898.

Miscellaneous

0.9.88 - 2025-01-15

Added

  • If nextest's keyboard input handler is enabled, pressing Enter now produces a summary line (e.g. Running [ 00:00:05] 131/297: 32 running, 131 passed, 1 skipped). This enables common use cases where Enter is pressed to mark a point in time.
  • On illumos, Ctrl-T (SIGINFO) is now supported as a way to query live status. Querying live status is also supported on BSDs with Ctrl-T, on any Unix via SIGUSR1, as well as by pressing the t key in interactive sessions.

Changed

  • If nextest is unable to parse --target (and in particular, a custom target), it now fails rather than printing a warning and assuming the host platform. This is being treated as a bugfix because the previous behavior was incorrect.

Fixed

  • Custom targets now respect target_family predicates like cfg(unix).
  • Nextest now exits cleanly if the progress bar is enabled and writing to standard error fails. This matches the behavior in case the progress bar is disabled.
  • If nextest is compiled with a system libzstd that doesn't have multithreading support, archive support no longer fails. Thanks Leandros for your first contribution!

0.9.87 - 2024-12-17

Changed

  • On Windows, if a Ctrl-C is received and running tests don't terminate within the grace period (default 10 seconds), they're now forcibly terminated via a job object. Previously, nextest would wait indefinitely for tests to exit, unlike the behavior on Unix platforms where tests are SIGKILLed after the grace period.
  • The UI has also been updated to make it clearer when tests are forcibly terminated on Windows.

Fixed

  • Fixed a race condition between test cancellation and new tests being started. Now, once cancellation has begun, no new tests (or retries) will be started.

0.9.86 - 2024-12-12

This is a substantial release with several new features. It's gone through a period of beta testing, but if you run into issues please file a bug!

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!

Extra arguments to the test binary

You can now pass in extra arguments to the test binary at runtime, via the run-extra-args configuration option. In combination with a custom test harness like libtest-mimic, this can be used to run tests on the main thread of the process.

For more information, see Passing in extra arguments.

Setup scripts in JUnit output

Setup scripts are now represented in the JUnit output. For more information, see Setup scripts in JUnit output.

Changed

Tokio task per test

Each test now has a separate Tokio task associated with it. This leads to greater reliability (each test's task can now panic independently), and is faster in repos with many small tests.

For example, in one test done against clap-rs/clap on Linux, the time reported by cargo nextest run goes down from 0.36 seconds to 0.23 seconds.

UI refresh

Several minor improvements to the user interface:

  • The progress bar and other UI elements use Unicode characters if available.
  • Pressing Ctrl-C twice now prints out a "Killing" message.
  • Some more minor improvements that should lead to a more cohesive user experience.

MSRV update

The MSRV for compiling nextest is now Rust 1.81. (The MSRV for running tests remains unchanged.)

Fixed

  • Fixed a bug where pressing two Ctrl-Cs in succession would not SIGKILL any running tests.
  • junit.store-success-output now works correctly—previously, storage of output is disabled unconditionally.
  • In JUnit output, the testsuite elements are now listed in the order they are first seen (IndexMap), rather than in random order (HashMap).
  • When adding extra files to an archive, nextest now ignores empty and . path components in the specification while joining the specified path. This normalizes paths, meaning 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 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!

  • If an I/O error occurs waiting for a test process to finish, standard output and standard error are now displayed correctly.

0.9.85 - 2024-11-26

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.

0.9.84 - 2024-11-15

Fixed

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

0.9.83 - 2024-11-15

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.

0.9.82 - 2024-10-28

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.

0.9.81 - 2024-10-06

Fixed

Fixed semantics of --exact to match Rust's libtest: --exact now makes it so that all filters passed in after -- (including --skip filters) are matched exactly.

0.9.80 - 2024-10-05

Added

Support for --skip and --exact as emulated test binary arguments. The semantics match those of libtest binaries.

For example, to run all tests other than those matching the substring slow_tests:

cargo nextest run -- --skip slow_tests

To run all tests matching either the substring my_test or the exact string exact_test:

cargo nextest run -- my_test --exact exact_test

Thanks to svix-jplatte for your first contribution!

0.9.79 - 2024-10-02

Added

  • Expanded version information: cargo nextest -V now shows commit and date information similar to rustc and cargo, and cargo nextest --version shows this information in long form.

Fixed

  • Nextest will now enable colors by default in more situations, particularly over SSH connections. For more information, see this issue.
  • Fixed a case of cargo metadata parsing with renamed packages (#1746).

0.9.78 - 2024-09-05

Added

For failing tests, if nextest finds text matching patterns that indicate failure, such as "thread panicked at", it now highlights those lines (if color is enabled).

Rust's libtest doesn't provide structured output for this, so nextest uses heuristics. These heuristics will be tweaked over time; to see what nextest would highlight, run cargo nextest debug extract highlight, and provide either --stdout and --stderr, or --combined if stdout and stderr are combined.

0.9.77 - 2024-08-28

Changed

A couple of UI changes:

  • default-set is now default-filter.
  • --bound=all is now --ignore-default-filter.

Sorry about the breakage here -- this should be the last of the changes.

0.9.76 - 2024-08-25

Added

  • A new --bound=all option disables the default set on the command line.
  • --run-ignored ignored-only has been shortened to --run-ignored only. (The old name still works as an alias.)

Fixed

  • Documentation links updated to point to the new website.

Changed

  • Previously, passing in any -E options would disable the default set. However in practice that was found to be too confusing, and this behavior has been removed. Instead, use --bound.

    This is technically a breaking change, but default sets aren't in wide use yet so this should have minimal impact.

0.9.75 - 2024-08-23

Added

  • Support for default sets of tests to run via the default-set configuration. See Running a subset of tests by default for more information.
  • A new --no-tests option controls the behavior of nextest when no tests are run. The possible values are pass, warn and fail. Per the behavior changed described in discussion #1646, the current default is warn, and it will change to fail in the future.

0.9.74 - 2024-08-18

Added

Warnings are now printed in the following cases:

  • If some tests are not run, e.g. due to --fail-fast.
  • If no tests are run.

Changed

  • Updated MSRV for compiling nextest to Rust 1.75.

Upcoming behavior changes

If no tests are run, nextest will start exiting with the advisory code 4 in versions released after 2024-11-18. See discussion #1646 for more.

0.9.73 - 2024-08-18

(This version was not released due to a publishing issue.)

0.9.72 - 2024-05-23

Fixed

Previously, nextest would be unable to run proc-macro tests in some circumstances:

  • On Windows, with rustup 1.27.2 and above
  • On all platforms, if cargo is used without rustup, or if the cargo-nextest binary is invoked directly

With this release, proc-macros tests now work in all circumstances. This is done by nextest detecting Rust libdirs for the host and target platforms, and adding them to the library path automatically.

(There's also the less-common case of test binaries compiled with -C prefer-dynamic. These situations now also work.)

See #267 and #1493 for more details.

Thanks to 06393993 for your first contribution!

Changed

As part of the above fix, libstd is now included in all archives. This makes archives around 4MB bigger, or around 8MB in cross-compilation scenarios. (It is possible to address this via config knobs -- if this is particularly bothersome to you, please post in #1515.)

0.9.71 - 2024-05-23

(This version was not published due to a release issue.)

0.9.70 - 2024-04-24

Added

  • Archives can now include extra paths in them. For example:

    [profile.default]
archive.include = [
    { path = "my-extra-path", relative-to = "target" }
]

    For more information, see Adding extra files to an archive.

    Thanks to @rukai for your first contribution!

  • You can now pass in --cargo-quiet twice to completely discard standard error for the Cargo commands run by nextest. This is equivalent to 2> /dev/null.

Fixed

  • The initial cargo metadata execution now passes in --frozen, --locked, --offline and --quiet if the corresponding flags are passed into nextest.
  • Previously, NEXTEST_HIDE_PROGRESS_BAR=1 did not work (only NEXTEST_HIDE_PROGRESS_BAR=true did). Now both 1 and true work.

Changed

  • Updated MSRV for compiling nextest to Rust 1.74.

0.9.69 - 2024-04-24

This release wasn't published due to a build issue.

0.9.68 - 2024-03-16

This is a maintenance release with many internal improvements, and preparation for future features.

Changed

  • Nextest binaries now ship with symbols, producing better stack traces. This is aligned with the behavior. See issue #1345 for more information.

  • Thanks to recent improvements, Miri is now significantly less taxing. As a result, nextest with Miri has been changed to use all threads by default. You can restore the old Miri behavior (run one test at a time) with -j1, or by setting in .config/nextest.toml:

    [profile.default-miri]
test-threads = 1

    Rules for heavy tests and test groups will continue to be followed with Miri.

    Thanks to Ben Kimock for driving the Miri improvements and updating nextest!

Misc

0.9.67 - 2024-01-09

Added

  • More work on machine-readable output for test runs: for failing tests, output is now included under the stdout field. This was a large effort which required figuring out how to combine stdout and stderr into the same buffer. Thanks again Jake for your contribution!

Fixed

  • On SIGTERM and SIGHUP, outputs for cancelled and failed tests are now displayed. (Output is still hidden on SIGINT to match typical user expectations.)

0.9.66 - 2023-12-10

Added

Experimental feature: machine-readable output for test runs

Nextest now has experimental support for machine-readable output during cargo nextest run invocations (#1086), in a format similar to cargo test's libtest JSON output. For more information, see the documentation.

Thanks Jake Shadle for your contribution!

OUT_DIR support

Improvements to build script OUT_DIR support:

  • Matching the behavior of cargo test, nextest now sets the OUT_DIR environment variable at runtime if there's a corresponding build script.

  • While creating archives, nextest now archives OUT_DIRs if:

    • The build script is for a crate in the workspace, and
    • There's at least one test binary for that crate.

    This is so that the OUT_DIR environment variable continues to be relevant for test runs out of archives.

    Currently, OUT_DIRs are only archived one level deep to avoid bloating archives too much. In the future, we may add configuration to archive more or less of the output directory. If you have a use case that would benefit from this, please file an issue.

Misc

  • The .crate files uploaded to crates.io now contain the LICENSE-APACHE and LICENSE-MIT license files. Thanks @musicinmybrain for your first contribution!

0.9.65 - 2023-12-10

This version was not released due to a build issue on illumos.

0.9.64 - 2023-12-03

Added

  • Stabilized and documented the binary ID format.
  • Support for glob matchers in filter expressions. For example, package(foo*) will match all tests whose names start with foo.
  • A new binary_id() predicate matches against the binary ID.

Changed

  • Unit tests in proc-macro crates now have a binary ID that consists of just the crate name, similar to unit tests in normal crates.

  • The default string matcher for the following predicates has changed from equality to glob:

    • Package-related matchers: package(), deps(), and rdeps()
    • Binary-related matchers: binary()

    The new binary_id() predicate also uses the glob matcher by default.

Fixed

  • Fixed a regression with some Cargo nightly-only features: see guppy-rs/guppy#174 for more details.

0.9.63 - 2023-11-17

Fixed

0.9.62 - 2023-11-14

Added

  • If you create a symlink manually named cargo-ntr and pointing to cargo-nextest, you can now shorten cargo nextest run to cargo ntr. In the future, this symlink will be automatically created at install time.

Changed

  • Deprecated test name filters passed in before --. For example, cargo nextest run my_test is deprecated; use cargo nextest run -- my_test instead. See #1109 for motivation and more information.
  • x86_64-unknown-linux-gnu builds are now performed using cargo zigbuild. The minimum glibc version remains unchanged at 2.27. Please file a bug report if you encounter any issues with this change.

Fixed

  • Fixed crashes under some Cargo edge cases, e.g. #1090.

0.9.61 - 2023-10-22

Changed

  • The grace period in slow-timeout.grace-period now applies to terminations as well. Thanks @kallisti-dev for your first contribution!

Fixed

  • JUnit output now strips ANSI escapes as well. Thanks @MaienM for your first contribution!

0.9.60 - 2023-10-22

This version was not released due to a packaging issue.

0.9.59 - 2023-09-27

Added

  • Experimental support for setup scripts. Please try them out, and provide feedback in the tracking issue!
  • Support for newer error messages generated by Rust 1.73.

Fixed

  • deps() and rdeps() predicates in per-test overrides were previously not working correctly. With this version they now work.

0.9.58 - 2023-09-20

Added

Fixed

  • Improved color support by pulling in zkat/supports-color#14. Now nextest should produce color more often when invoked over SSH.

0.9.57 - 2023-08-02

Fixed

  • Fixed case when .config/nextest.toml isn't present (#926).

0.9.56 - 2023-08-02

Fixed

  • nextest-version is now parsed in a separate pass. This means that error reporting in case there's an incompatible config is now better.

0.9.55 - 2023-07-29

Added

  • Support for Cargo's --timings option (#903).
  • Support for required and recommended versions, via a new nextest-version top-level configuration option. See Minimum nextest versions for more.

Fixed

  • Detect tests if debug level line-tables-only is passed in (#910).

0.9.54 - 2023-06-25

Added

Custom targets

  • Nextest now supports custom targets specified via --target, CARGO_BUILD_TARGET, or configuration. See the Rust Embedonomicon for how to create a custom target.
  • For per-test overrides, platform filters now support custom target triples.

0.9.53 - 2023-05-15

Added

  • Filter expressions in TOML files can now be specified as multiline TOML strings. For example:
[[profile.default.overrides]]
filter = '''
  test(my_test)
  | package(my-package)
'''
# ...

Changed

  • show-config test-groups now shows a clean representation of filter expressions, to enable printing out multiline expressions neatly.

0.9.52 - 2023-05-04

Fixed

  • Updated dependencies to resolve a build issue on Android (#862).

0.9.51 - 2023-03-19

Changed

  • The definition of threads-required has changed slightly. Previously, it was possible for global and group concurrency limits to be exceeded in some circumstances. Now, concurrency limits are never exceeded. This enables some new use cases, such as being able to declare that a test is mutually exclusive with all other tests globally.

0.9.50 - 2023-03-13

Added

  • cargo nextest r added as a shortcut for cargo nextest run.

Fixed

  • Switched to using OpenSSL on RISC-V, since ring isn't available on that platform.

0.9.49 - 2023-01-13

Added

  • New configuration settings added to JUnit reports: junit.store-success-output (defaults to false) and junit.store-failure-output (defaults to true) control whether output for passing and failing tests should be stored in the JUnit report.
  • The following configuration options can now be specified as per-test overrides:
    • success-output and failure-output.
    • junit.store-success-output and junit.store-failure-output.

0.9.48 - 2023-01-02

Added

  • You can now mark certain groups of tests to be run with a limited amount of concurrency within the group. This can be used to run tests within a group serially, similar to the serial_test crate.

    For more about test groups, see Test groups and mutual exclusion.

  • A new show-config test-groups command shows test groups currently in effect. (show-config will be broadened to show other kinds of configuration in future releases.)

  • Nextest now warns you if you've defined a profile in the default- namespace that isn't already known. Any profile names starting with default- are reserved for future use.

    Thanks Marcelo Nicolas Gomez Rivera for your first contribution!

Changed

  • On Unix platforms, nextest now uses a new double-spawn test execution mode. This mode resolves some race conditions around signal handling without an apparent performance cost.

    This mode is not expected to cause any issues. However, if it does, you can turn it off by setting NEXTEST_DOUBLE_SPAWN=0 in your environment. (Please report an issue if it does!)

  • MSRV updated to Rust 1.64.

0.9.47 - 2022-12-10

Fixed

  • cargo nextest run -E 'deps(foo) queries now work again. Thanks Simon Paitrault for your first contribution!

0.9.46 - 2022-12-10

This version was not published due to a packaging issue.

0.9.45 - 2022-12-04

Added

  • Support for listing and running tests in examples with the --examples and --example <EXAMPLE> command-line arguments. Thanks Jed Brown for your first contribution!
  • Pre-built binaries are now available for FreeBSD and illumos. Due to GitHub Actions limitations, nextest is not tested on these platforms and might be broken.

0.9.44 - 2022-11-23

Added

Double-spawning test processes

On Unix platforms, a new experimental "double-spawn" approach to running test binaries has been added. With the double-spawn approach, when listing or running tests, nextest will no longer spawn test processes directly. Instead, nextest will first spawn a copy of itself, which will do some initial setup work and then exec the test process.

The double-spawn approach is currently disabled by default. It can be enabled by setting NEXTEST_EXPERIMENTAL_DOUBLE_SPAWN=1 in your environment.

The double-spawn approach will soon be enabled the default.

Pausing and resuming test runs

Nextest now has initial support for handling SIGTSTP (Ctrl-Z) and SIGCONT (fg). On SIGTSTP (e.g. when Ctrl-Z is pressed), all running tests and timers are paused, and nextest is suspended. On SIGCONT (e.g. when fg is run), tests and timers are resumed.

Note that, by default, pressing Ctrl-Z in the middle of a test run can lead to nextest runs hanging sometimes. These nondeterministic hangs will not happen if both of the following are true:

  • The double-spawn approach is enabled (see above) with NEXTEST_EXPERIMENTAL_DOUBLE_SPAWN=1.

Call for testing: Please try out the double-spawn approach by setting NEXTEST_EXPERIMENTAL_DOUBLE_SPAWN=1 in your environment. It has been extensively tested and should not cause any breakages, but if it does, please report an issue. Thank you!

Fixed

  • Fixed an issue with nextest hanging on Windows with spawned processes that outlive the test (#656). Thanks to Chip Senkbeil for reporting it and providing a minimal example!

0.9.43 - 2022-11-04

Nextest is now built with Rust 1.65. This version of Rust is the first one to spawn processes using posix_spawn rather than fork/exec on macOS, which should lead to performance benefits in some cases.

For example, on an M1 Mac Mini, with the clap repository at 520145e, and the command cargo nextest run -E 'not (test(ui_tests) + test(example_tests))':

  • Before: 0.636 seconds
  • After: 0.284 seconds (2.23x faster)

This is a best-case scenario; tests that take longer to run will generally benefit less.

Added

  • The threads-required configuration now supports the values "num-cpus", for the total number of logical CPUs available, and "num-test-threads", for the number of test threads nextest is running with.
  • Nextest now prints a warning if a configuration setting is unknown.

Fixed

  • Configuring retries = 0 now works correctly. Thanks xxchan for your first contribution!

0.9.42 - 2022-11-01

Added

0.9.41 - 2022-11-01

This release ran into an issue during publishing and was skipped.

0.9.40 - 2022-10-25

Added

  • Overrides can now be restricted to certain platforms, using triples or cfg() expressions. For example, to add retries, but only on macOS:

    [[profile.default.overrides]]
platform = 'cfg(target_os = "macos")'
retries = 3

    For an override to match, platform and filter (if specified) must both be true for a given test. While cross-compiling code, platform is matched against the host platform for host tests, and against the target platform for target tests.

  • Nextest now reads environment variables specified in the [env] section from .cargo/config.toml files. The full syntax is supported including force and relative.

    Thanks to Waleed Khan for your first contribution!

  • Nextest now sets the CARGO_PKG_RUST_VERSION environment variable when it runs tests. For cargo test this was added in Rust 1.64, but nextest sets it across all versions of Rust.

0.9.39 - 2022-10-14

Added

  • On Unix platforms, if a process times out, nextest attempts to terminate it gracefully by sending it SIGTERM, waiting for a grace period of 10 seconds, and then sending it SIGKILL. A custom grace period can now be specified through the slow-timeout.grace-period parameter. For more information, see How nextest terminates tests.

    Thanks to Ben Kimock for your first contribution!

Internal improvements

  • Updated clap to version 4.0.

0.9.38 - 2022-10-05

Added

  • Test retries now support fixed delays and exponential backoffs, with optional jitter. See Delays and backoff for more information. Thanks Tomas Olvecky for your first contribution!

Internal improvements

  • Reading test data from standard output and standard error no longer buffers twice, just once. Thanks Jiahao XU for your first contribution!

Note to distributors: now that Rust 1.64 is out, process_group_bootstrap_hack is no longer supported or required. Please remove the following environment variables if you've set them:

  • RUSTC_BOOTSTRAP=1
  • RUSTFLAGS='--cfg process_group --cfg process_group_bootstrap_hack'

0.9.37 - 2022-09-30

Added

  • Support for a negative value for --test-threads/-j, matching support in recent versions of Cargo. A value of -1 means the number of logical CPUs minus 1, and so on. Thanks Onigbinde Oluwamuyiwa Elijah for your first contribution!
  • Add a note to the help text for --test-threads indicating that its default value is obtained from the profile. Thanks jiangying for your first contribution!

Changed

  • Internal dependency target-spec bumped to 1.2.0 -- this means that newer versions of the windows crate are now supported.
  • MSRV updated to Rust 1.62.

0.9.36 - 2022-09-07

Added

  • A new --hide-progress-bar option (environment variable NEXTEST_HIDE_PROGRESS_BAR) forces the progress bar to be hidden. Thanks Remo Senekowitsch for your first contribution!

Changed

  • Nextest now prints out a list of failing and flaky tests at the end of output by default (the final-status-level config is set to flaky).
  • The progress bar is now hidden if a CI environment is detected.

0.9.35 - 2022-08-17

Added

  • Support for the --config argument, stabilized in Rust 1.63. This option is used to configure Cargo, not nextest. This argument is passed through to Cargo, and is also used by nextest to determine e.g. the target runner for a platform.

    --config is also how Miri communicates with nextest.

0.9.34 - 2022-08-12

Added

  • For cargo nextest self update, added -f as a short-form alias for --force.

Fixed

  • Tests are no longer retried after a run is canceled. Thanks iskyzh for your contribution!

0.9.33 - 2022-07-31

Fixed

  • Fixed regression in cargo-nextest 0.9.32 where it no longer produced any output if stderr wasn't a terminal.

0.9.32 - 2022-07-30

Added

  • cargo nextest run now has a new --no-run feature to build but not run tests. (This was previously achievable with cargo nextest list -E 'none()', but is more intuitive this way.)
  • Pre-built binaries are now available for i686 Windows. Thanks Guiguiprim!

Internal improvements

  • Filter expression evaluation now uses a stack machine via the recursion crate. Thanks Inanna for your first contribution!

0.9.31 - 2022-07-27

Added

  • Nextest sets a new NEXTEST_RUN_ID environment variable with a UUID for a test run. All tests run within a single invocation of cargo nextest run will set the same run ID. Thanks mitsuhiko for your first contribution!

0.9.30 - 2022-07-25

Fixed

  • Fixed target runners specified as relative paths.

  • On Unix, cargo-nextest's performance had regressed (by 3x on clap) due to the change introduced in version 0.9.29 to put each test process into its own process group. In this version, this regression has been fixed, but only if you're using the pre-built binaries or building on Rust 1.64+ (currently in nightly).

    Note to distributors: to fix this regression while building with stable Rust 1.62, set the following environment variables:

    • RUSTC_BOOTSTRAP=1
    • RUSTFLAGS='--cfg process_group --cfg process_group_bootstrap_hack'

    This is temporary until the process_set_process_group feature is stabilized in Rust 1.64.

0.9.29 - 2022-07-24

Added

  • On Unix, each test process is now put into its own process group. If a test times out or Ctrl-C is pressed, the entire process group is signaled. This means that most subprocesses spawned by tests are also killed.

    However, because process groups aren't nested, if a test creates a process group itself, those groups won't be signaled. This is a relatively uncommon situation.

  • On Windows, each test process is now associated with a job object. On timeouts, the entire job object is terminated. Since job objects are nested in recent versions of Windows, this should result in all subprocesses spawned by tests being killed.

    (On Windows, the Ctrl-C behavior hasn't changed. Nextest also doesn't do graceful shutdowns on Windows yet, though this may change in the future.)

  • Nextest can now parse Cargo configs specified via the unstable --config option.
  • Nextest now publishes binaries for aarch64-unknown-linux-gnu (#398) and x86_64-unknown-linux-musl (#399). Thanks messense and Teymour for your first contributions!

Fixed

  • Per-test overrides are now additive across configuration files (including tool-specific configuration files).

0.9.28 - 2022-07-22

This is a quick hotfix release to ensure that the right tokio features are enabled under default-no-update.

0.9.27 - 2022-07-22

This is a major architectural rework of nextest. We've tested it thoroughly to the best of our ability, but if you see regressions please report them!

If you encounter a regression, you can temporarily pin nextest to the previous version in CI. If you're on GitHub Actions and are using taiki-e/install-action, use this instead:

- uses: taiki-e/install-action@v1
- with:
    tool: nextest
    version: 0.9.26

Added

  • Nextest now works with the Miri interpreter. Use cargo miri nextest run to run your tests with Miri.
  • Nextest now detects some situations where tests leak subprocesses. Previously, these situations would cause nextest to hang.
  • Per-test overrides now support slow-timeout and the new leak-timeout config parameter.
  • A new option --tool-config-file allows tools that wrap nextest to specify custom config settings, while still prioritizing repository-specific configuration.

Changed

  • Major internal change: The nextest list and run steps now use Tokio. This change enables the leak detection described above.
  • The list step now runs list commands in parallel. This should result in speedups in most cases.

Fixed

  • Nextest now redirects standard input during test runs to /dev/null (or NUL on Windows). Most tests do not read from standard input, but if a test does, it will no longer cause nextest to hang.
  • On Windows, nextest configures standard input, standard output and standard error to not be inherited. This prevents some kinds of test hangs on Windows.
  • If a dynamic library link path doesn't exist, nextest no longer adds it to LD_LIBRARY_PATH or equivalent. This should have no practical effect.
  • Archiving tests now works even if the target directory is not called "target".

0.9.26 - 2022-07-14

This is a quick hotfix release to update the version of nextest-metadata, to which a breaking change was accidentally committed.

0.9.25 - 2022-07-13

This is a major release with several new features.

Filter expressions

Filter expressions are now ready for production. For example, to run all tests in nextest-runner and all its transitive dependencies within the workspace:

cargo nextest run -E 'deps(nextest-runner)'

This release includes a number of additions and changes to filter expressions.

Added

  • The expression language supports several new predicates:
    • kind(name-matcher): include all tests in binary kinds (e.g. lib, test, bench) matching name-matcher.
    • binary(name-matcher): include all tests in binary names matching name-matcher.
    • platform(host) or platform(target): include all tests that are built for the host or target platform, respectively.

Changed

  • If a filter expression is guaranteed not to match a particular binary, it will not be listed by nextest. (This allows platform(host) and platform(target) to work correctly.)
  • If both filter expressions and standard substring filters are passed in, a test must match filter expressions AND substring filters to be executed. For example:
cargo nextest run -E 'package(nextest-runner)' test_foo test_bar

This will execute only the tests in nextest-runner that match test_foo or test_bar.

Per-test overrides

Nextest now supports per-test overrides. These overrides let you customize settings for subsets of tests. For example, to retry tests that contain the substring test_e2e 3 times:

[[profile.default.overrides]]
filter = "test(test_e2e)"
retries = 3

Currently, only retries are supported. In the future, more kinds of customization will be added.

Other changes

  • A new environment variable NEXTEST_RETRIES controls the number of retries tests are run with. In terms of precedence, this slots in between the command-line --retries option and per-test overrides for retries.
  • cargo nextest list now hides skipped tests and binaries by default. To print out skipped tests and binaries, use cargo nextest list --verbose.
  • The Machine-readable output for cargo nextest list now contains a new "status" key. By default, this is set to "listed", and for binaries that aren't run because they don't match expression filters this is set to "skipped".
  • The --platform-filter option is deprecated, though it will keep working for all versions within the nextest 0.9 series. Use -E 'platform(host)' or -E 'platform(target)' instead.
  • cargo nextest run -- --skip and --exact now suggest using a filter expression instead.

0.9.24 - 2022-07-01

Added

  • New config option profile.<profile-name>.test-threads controls the number of tests run simultaneously. This option accepts either an integer with the number of threads, or the string "num-cpus" (default) for the number of logical CPUs. As usual, this option is overridden by --test-threads and NEXTEST_TEST_THREADS, in that order.
  • The command-line --test-threads option and the NEXTEST_TEST_THREADS environment variable now accept num-cpus as their argument.
  • nextest now works with cargo binstall (#332). Thanks @remoun for your first contribution!

Fixed

  • Within JUnit XML, test failure descriptions (text nodes for <failure> and <error> tags) now have invalid ANSI escape codes stripped from their output.

0.9.23 - 2022-06-26

Added

  • On Windows, nextest now detects tests that abort due to e.g. an access violation (segfault) and prints their status as "ABORT" rather than "FAIL", along with an explanatory message on the next line.
  • Improved JUnit support: nextest now heuristically detects stack traces and adds them to the text node of the <failure> element (#311).

Changed

  • Errors that happen while writing data to the output now have a new documented exit code: [WRITE_OUTPUT_ERROR].

0.9.22 - 2022-06-21

Added

  • Benchmarks are now treated as normal tests. (#283, thanks @tabokie for your contribution!).

    Note that criterion.rs benchmarks are currently incompatible with nextest (#96) -- this change doesn't have any effect on that.

  • Added -F as a shortcut for --features, mirroring an upcoming addition to Cargo 1.62 (#287, thanks Alexendoo for your first contribution!)

Changed

  • If nextest's output is colorized, it no longer strips ANSI escape codes from test runs.

0.9.21 - 2022-06-17

Added

  • On Unix, tests that fail due to a signal (e.g. SIGSEGV) will print out the name of the signal rather than the generic "FAIL".
  • cargo-nextest has a new "default-no-update" feature that will contain all default features except for self-update. If you're distributing nextest or installing it in CI, the recommended, forward-compatible way to build cargo-nextest is with --no-default-features --features default-no-update.

Changed

  • Progress bars now take up the entire width of the screen. This prevents issues with the bar wrapping around on terminals that aren't wide enough.

0.9.20 - 2022-06-13

Fixed

  • Account for skipped tests when determining the length of the progress bar.

0.9.19 - 2022-06-13

Added

  • Nextest can now update itself! Once this version is installed, simply run cargo nextest self update to update to the latest version.

    Note to distributors: you can disable self-update by building cargo-nextest with --no-default-features.

  • Partial, emulated support for test binary arguments passed in after cargo nextest run -- (#265, thanks @tabokie for your contribution!).

    For example, cargo nextest run -- my_test --ignored will run ignored tests containing my_test, similar to cargo test -- my_test --ignored.

    Support is limited to test names, --ignored and --include-ignored.

    Note to integrators: to reliably disable all argument parsing, pass in -- twice. For example, cargo nextest run -- -- <filters...>.

Fixed

  • Better detection for cross-compilation -- now look through the CARGO_BUILD_TARGET environment variable, and Cargo configuration as well. The --target option is still preferred.
  • Slow and flaky tests are now printed out properly in the final status output (#270).

This is a test release.

0.9.18 - 2022-06-08

Added

  • Support for terminating tests if they take too long, via the configuration parameter slow-timeout.terminate-after. For example, to time out after 120 seconds:

    slow-timeout = { period = "60s", terminate-after = 2 }

    Thanks steveeJ for your contribution (#214)!

Fixed

  • Improved support for reusing builds: produce better error messages if the workspace's source is missing.

0.9.17 - 2022-06-07

This release contains a number of user experience improvements.

Added

  • If producing output to an interactive terminal, nextest now prints out its status as a progress bar. This makes it easy to see the status of a test run at a glance.
  • Nextest's configuration has a new final-status-level option which can be used to print out some statuses at the end of a run (defaults to none). On the command line, this can be overridden with the --final-status-level argument or NEXTEST_FINAL_STATUS_LEVEL in the environment.
  • If a target runner is in use, nextest now prints out its name and the environment variable or config file the definition was obtained from.

Changed

  • If the creation of a test list fails, nextest now prints a more descriptive error message, and exits with the exit code 104 ([TEST_LIST_CREATION_FAILED]).

0.9.16 - 2022-06-02

Added

Fixed

  • While archiving build artifacts, work around some libraries producing linked paths that don't exist (#247). Print a warning for those paths instead of failing.

Changed

  • Build artifact archives no longer recurse into linked path subdirectories. This is not a behavioral change because LD_LIBRARY_PATH and other similar variables do not recurse into subdirectories either.

0.9.15 - 2022-05-31

Added

  • Improved support for reusing builds:
    • New command cargo nextest archive automatically archives test binaries and other relevant files after building tests. Currently the .tar.zst format is supported.
    • New option cargo nextest run --archive-file automatically extracts archives before running the tests within them.
    • New runtime environment variable NEXTEST_BIN_EXE_<name> is set to the absolute path to a binary target's executable, taking path remapping into account. This is equivalent to [CARGO_BIN_EXE_<name>], except this is set at runtime.
    • cargo nextest list --list-type binaries-only now records information about non-test binaries as well.

Fixed

Fix for experimental feature filter expressions:

  • Fix test filtering when expression filters are set but name-based filters aren't.

0.9.14 - 2022-04-18

Fixed

Fixes related to path remapping:

  • Directories passed into --workspace-remap and --target-dir-remap are now canonicalized.
  • If the workspace directory is remapped, CARGO_MANIFEST_DIR in tests' runtime environment is set to the new directory.

0.9.13 - 2022-04-16

Added

  • Support for reusing builds is now production-ready. Build on one machine and run tests on another, including cross-compiling and test partitioning.

    To see how builds can be reused in GitHub Actions, see this example.

  • Experimental support for filter expressions, allowing fine-grained specifications for which tests to run.

Thanks to Guiguiprim for their fantastic work implementing both of these.

0.9.12 - 2022-03-22

Added

Fixed

  • Test binaries that link to dynamic libraries built by Cargo now work correctly (#82).
  • Crates with no tests are now skipped while computing padding widths in the reporter (#125).

Changed

  • MSRV updated to Rust 1.56.
  • For experimental feature reusing builds:
    • Change --binaries-dir-remap to --target-dir-remap and expect that the entire target directory is archived.
    • Support linking to dynamic libraries (#82).

0.9.11 - 2022-03-09

Fixed

0.9.10 - 2022-03-07

Thanks to Guiguiprim for their contributions to this release!

Added

  • A new --platform-filter option filters tests by the platform they run on (target or host).
  • cargo nextest list has a new --list-type option, with values full (the default, same as today) and binaries-only (list out binaries without querying them for the tests they contain).
  • Nextest executions done as a separate process per test (currently the only supported method, though this might change in the future) set the environment variable NEXTEST_PROCESS_MODE=process-per-test.

New experimental features

  • Nextest can now reuse builds across invocations and machines. This is an experimental feature, and feedback is welcome in #98!

Changed

  • The target runner is now build-platform-specific; test binaries built for the host platform will be run by the target runner variable defined for the host, and similarly for the target platform.

0.9.9 - 2022-03-03

Added

  • Updates for Rust 1.59:
    • Support abbreviating --release as -r (Cargo #10133).
    • Stabilize future-incompat-report (Cargo #10165).
    • Update builtin list of targets (used by the target runner) to Rust 1.59.

0.9.8 - 2022-02-23

Fixed

  • Target runners of the form runner = ["bin-name", "--arg1", ...] are now parsed correctly (#75).
  • Binary IDs for [[bin]] and [[example]] tests are now unique, in the format <crate-name>::bin/<binary-name> and <crate-name>::test/<binary-name> respectively (#76).

0.9.7 - 2022-02-23

Fixed

  • If parsing target runner configuration fails, warn and proceed without a target runner rather than erroring out.

Known issues

  • Parsing an array of strings for the target runner currently fails: #73. A fix is being worked on in #75.

0.9.6 - 2022-02-22

Added

0.9.5 - 2022-02-20

Fixed

  • Updated nextest-runner to 0.1.2, fixing cyan coloring of module paths (#52).

0.9.4 - 2022-02-16

The big new change is that release binaries are now available! Head over to Pre-built binaries for more.

Added

  • In test output, module paths are now colored cyan (#42).

Fixed

  • While querying binaries to list tests, lines ending with ": benchmark" will now be ignored (#46).

0.9.3 - 2022-02-14

Fixed

  • Add a BufWriter around stderr for the reporter, reducing the number of syscalls and fixing issues around output overlap on Windows (#35). Thanks @fdncred for reporting this!

0.9.2 - 2022-02-14

Fixed

  • Running cargo nextest from within a crate now runs tests for just that crate, similar to cargo test. Thanks Yaron Wittenstein for reporting this!

0.9.1 - 2022-02-14

Fixed

  • Updated nextest-runner to 0.1.1, fixing builds on Rust 1.54.

0.9.0 - 2022-02-14

Initial release. Happy Valentine's day!

Added

Supported in this initial release: