nextest-runner 0.96.0

nextest-runner-0.96.0

[nextest-runner] version 0.96.0

cargo-nextest 0.9.114

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 this table for a comparison of behaviors.

nextest-runner 0.95.0

nextest-runner-0.95.0

[nextest-runner] version 0.95.0

cargo-nextest 0.9.113

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 done by nextest.

  Nextest's debugger support will likely see some iteration and improvements over time. If it's missing a feature, please open a feature request, or even better, send a pull request!

• Nextest now sets NEXTEST_BIN_EXE_* environment variables with hyphens in binary names replaced by underscores, in addition to the existing variables with hyphens. This works around some shells and debuggers that drop environment variables containing hyphens. (#2777)

Fixed

• Fixed a panic when attempting to display progress during retries. (#2771)
• With stress tests, the progress bar no longer overwrites unrelated output. (#2765)
• During the list phase, invalid output lines with control characters in them are now properly escaped. (#2772)

Other

• Nextest's GitHub releases are now marked immutable, so for a particular version, its release binaries can't be changed by anybody after publication. (Release binaries have never changed as a matter of policy. The improvement here is that for 0.9.113 and future versions, this fact is now cryptographically attested by GitHub.)

cargo-nextest 0.9.112

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 done by nextest.

  Nextest's debugger support will likely see some iteration and improvements over time. If it's missing a feature, please open a feature request, or even better, send a pull request!

• Nextest now sets NEXTEST_BIN_EXE_* environment variables with hyphens in binary names replaced by underscores, in addition to the existing variables with hyphens. This works around some shells and debuggers that drop environment variables containing hyphens. (#2777)

Fixed

• Fixed a panic when attempting to display progress during retries. (#2771)
• With stress tests, the progress bar no longer overwrites unrelated output. (#2765)
• During the list phase, invalid output lines with control characters in them are now properly escaped. (#2772)

cargo-nextest 0.9.113-b.1

This is a test release.

nextest-runner 0.94.0

nextest-runner-0.94.0

[nextest-runner] version 0.94.0

cargo-nextest 0.9.111

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 running tests as soon as the first test fails.

Changed

• In interactive terminals, nextest now shows 8 running tests by default underneath the progress bar. Control the maximum number of tests displayed with the --max-progress-running option.

  As part of this change, --show-progress=running is now an alias for --show-progress=bar. To only show running tests, use --show-progress=only.

• Non-UTF-8 test output is now encoded with String::from_utf8_lossy before being printed out to the terminal. This should generally not be a visible change, since most tests produce UTF-8 output.

• When the progress bar is displayed, nextest now writes to terminal output every 50ms.

Fixed

• A number of performance improvements to running test output. Thanks glehmann for your work on polishing this feature!

nextest-runner 0.93.0

nextest-runner-0.93.0

[nextest-runner] version 0.93.0

cargo-nextest 0.9.110

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 progress bar now stays in place more often, providing a smoother visual experience.

Changed

• MSRV for building nextest updated to Rust 1.88.

Internal improvements

• USDT probes now include additional context: global_slot, group_slot, and test_group fields for test attempt events.
• Miscellaneous performance improvements to --show-progress=running and only.