A next-generation test runner for Rust.
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
.
cargo metadata
execution now passes in --frozen
, --locked
, --offline
and --quiet
if the corresponding flags are passed into nextest.NEXTEST_HIDE_PROGRESS_BAR=1
did not work (only NEXTEST_HIDE_PROGRESS_BAR=true
did). Now both 1
and true
work.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
.
cargo metadata
execution now passes in --frozen
, --locked
, --offline
and --quiet
if the corresponding flags are passed into nextest.NEXTEST_HIDE_PROGRESS_BAR=1
did not work (only NEXTEST_HIDE_PROGRESS_BAR=true
did). Now both 1
and true
work.See the changelog for cargo-nextest 0.9.69.
This is a maintenance release with many internal improvements, and preparation for future features.
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!
This is a maintenance release with many internal improvements, and preparation for future features.
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!
This is a maintenance release with many internal improvements, and preparation for future features.
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!
See the changelog for cargo-nextest 0.9.68.
This is a test release.
This is a test release.
See the changelog for cargo-nextest 0.9.68.