winget install --id nextest.cargo-nextestAbout cargo-nextest
A next-generation test runner for Rust.
What's new in 0.9.143
Added - A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#885) Thanks to liangfu for your first contribution! - While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus software that scans each test binary before it runs. (#3471) - The binaries metadata (used by archives and --binaries-metadata) now records whether Cargo built each non-test binary for the host or the target platform. Future versions of nextest will use this to configure environment variables correctly in cross-compilation scenarios. (#3520) Changed - Nextest now orders the dynamic library search path the way current versions of Cargo do, with the Cargo artifact directory ahead of the deps directory. Previously the two were reversed, so a test could potentially resolve a dylib to a different copy than cargo test would. (Cargo swapped the two in 1.93.) Fixed - Nextest now computes the dynamic library search path correctly under build directory layout v2, which became the default on nightly Rust on 2026-07-30. Previously, tests that linked against a dylib dependency failed to start because the dynamic library could not be found. - When Cargo's build.build-dir is configured, nextest now adds the Cargo artifact directory (where final artifacts like binaries and dynamic libraries are uplifted to) instead of the build directory (for intermediate artifacts) to the dynamic library sea...
Version history
| Version | Updated | Notes |
|---|---|---|
| 0.9.143 | Unknown | Added - A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#885) Thanks to liangfu for your first contributio... |
| 0.9.140 | Unknown | Added - A new cargo nextest help <topic> subcommand renders reference documentation directly in the terminal. The available topics are: - filterset (alias filtersets): the filterset DSL reference - repo-config: the repos... |
| 0.9.138 | Unknown | Added - Nextest now sets the following environment variables during the list phase, not just the run phase: - NEXTEST_VERSION - NEXTEST_REQUIRED_VERSION - NEXTEST_RECOMMENDED_VERSION - NEXTEST_RUN_ID - NEXTEST_BINARY_ID... |
| 0.9.137 | Unknown | 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... |
| 0.9.136 | Unknown | 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 nextes... |
| 0.9.135 | Unknown | Fixed an issue with a from-crates.io build. |
| 0.9.133 | Unknown | Added - Nextest now supports a group() filterset predicate for CLI filter expressions, allowing tests to be listed or run by their assigned test group. (#3273) For example, to run all tests in a specific group: cargo nex... |
| 0.9.132 | Unknown | Update aws-lc-sys to 0.39.0 to address GHSA-394x-vwmw-crm3. |
| 0.9.131 | Unknown | Added - Setup scripts and wrapper scripts can now specify per-command environment variables via the env field in the command configuration. (#3001) For example: [scripts.setup.script1] command = { command-line = "cargo r... |
| 0.9.130 | Unknown | Added - Nextest now sets several new environment variables for tests and setup scripts: (#3103) - NEXTEST_VERSION: the current nextest version as a semver string. - NEXTEST_REQUIRED_VERSION and NEXTEST_RECOMMENDED_VERSIO... |
| 0.9.129 | Unknown | Changed - --show-progress=only now behaves like the default auto in non-interactive mode, showing successful tests with a counter. This change was made because only is primarily intended for interactive scenarios. (#3087... |
| 0.9.128 | Unknown | Fixed Updated the zip crate to 8.0.0 since versions 7.3.0 and 7.4.0 were yanked. |
| 0.9.121 | Unknown | Fixed - In custom target JSONs, panic-strategy = "immediate-abort" now parses correctly (#2922). |
| 0.9.120 | Unknown | Added - Support for using a pager like less with nextest's output. Currently supported are: - cargo nextest list - cargo nextest show-config test-groups - -h and --help commands The pager support is closely modeled after... |
| 0.9.115 | Unknown | Added - Nextest profiles now support inheritance via the inherits key. For example: [profile.ci] retries = 2 [profile.ci-extended] inherits = "ci" slow-timeout = "120s" Thanks asder8215 for your first contribution! (#278... |
| 0.9.114 | Unknown | Added - A new config option --tracer enables running a test under a system call tracer like strace or truss. This mode is similar to --debugger added in version 0.9.113, but is optimized for non-interactive sessions. See... |
| 0.9.113 | Unknown | Added - Nextest now supports running tests under a debugger. Use --debugger to run a single test under gdb, lldb, WinDbg, CodeLLDB in Visual Studio Code, and other debuggers, while preserving all the environment setup do... |
| 0.9.111 | Unknown | Added - Nextest now supports immediately terminating currently-running tests on failure. Set fail-fast = { max-fail = 1, terminate = "immediate" } in your configuration, or use --max-fail=1:immediate, to terminate runnin... |
| 0.9.110 | Unknown | Added - OSC 9;4 in-terminal progress bars are automatically enabled when the Ghostty terminal is detected. Thanks adamchalmers and RGBCube for your first contribution! Fixed - With --show-progress=running, the global pro... |
| 0.9.109 | Unknown | Added - A new running progress mode that shows currently running tests in addition to the progress bar. Use --show-progress=running to see both running tests and information about successful tests, or --show-progress=onl... |