nextest-runner

Changed

See the changelog for cargo-nextest 0.9.39.

Changed

See the changelog for cargo-nextest 0.9.38.

Changed

See the changelog for cargo-nextest 0.9.37.

Changed

See the changelog for cargo-nextest 0.9.36.

Changed

• guppy updated to 0.19.1.

Changed

See the changelog for cargo-nextest 0.9.34.

Fixed

• Reverted indicatif to 0.16.2 to fix regression where nextest no longer produced any output if stderr wasn't a terminal.

Changed

• nextest-metadata updated to 0.15.0.

Changed

See the changelog for cargo-nextest 0.9.31.

Changed

See the changelog for cargo-nextest 0.9.30.

Changed

See the changelog for cargo-nextest 0.9.29.

Changed

See the changelog for cargo-nextest 0.9.27.

Changed

• nextest-metadata updated to 0.5.0.

See the changelog for cargo-nextest 0.9.25.

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.

Fixed

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

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

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.

Changed

• If nextest's output is colorized, it no longer strips ANSI escape codes from test runs.
• quick-junit updated to 0.2.0.

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

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.

Fixed

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

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

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

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.

Changed

• Errors are now defined with thiserror. Some minor API changes were required for the migration.

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

Added

• Nextest now sets NEXTEST_LD_* and NEXTEST_DYLD_* environment variables to work around macOS System Integrity Protection sanitization.

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.

Added

• Support for creating and running archives of test binaries.
  • Most of the new logic is within a new reuse_build module.
• Non-test binaries and dynamic libraries are now recorded in BinaryList.

Fixed

Fix for experimental feature filter expressions:

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

Changed

• MSRV bumped to Rust 1.59.

Fixed

• PathMapper now canonicalizes the remapped workspace and target directories (and returns an error if that was unsuccessful).
• If the workspace directory is remapped, CARGO_MANIFEST_DIR in tests' runtime environment is set to the new directory.

Added

• Experimental support for filter expressions.

Added

• BinaryList and TestList have a new member called rust_build_meta, which returns Rust build-related metadata for a binary list or test list. This currently contains the target directory, the base output directories, and paths to search for dynamic libraries in relative to the target directory.

Changed

• MSRV bumped to Rust 1.56.

Thanks to Guiguiprim for their contributions to this release!

Added

• Filter test binaries by the build platform they're for (target or host).
• Experimental support for reusing build artifacts between the build and run steps.
• 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.

Changed

• TargetRunner now has separate handling for the target and host platforms. As part of this, a new struct PlatformRunner represents a target runner for a single platform.

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

• Improvements to TargetRunnerError message display: source errors are no longer displayed directly, only in "caused by".

Added

• Support for target runners.

Added

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

Changed

• Updated quick-junit to 0.1.5, fixing builds on Rust 1.54.

• Initial version.