Skip to content

Releases: nextest-rs/nextest

nextest-runner 0.61.0

05 Sep 22:25
Compare
Choose a tag to compare

nextest-metadata 0.12.1

05 Sep 22:23
Compare
Choose a tag to compare

Internal dependency updates.

cargo-nextest 0.9.78

05 Sep 22:37
Compare
Choose a tag to compare

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.

nextest-runner 0.60.0

28 Aug 21:32
Compare
Choose a tag to compare

nextest-metadata 0.12.0

28 Aug 21:29
Compare
Choose a tag to compare

Changed

  • Renamed references from "default-set" to "default-filter" to match cargo-nextest changes.

Removed

  • NextestExitCode::INVALID_FILTER_EXPRESSION has been renamed to INVALID_FILTERSET.

nextest-filtering 0.12.0

28 Aug 21:29
Compare
Choose a tag to compare

Changed

  • Renamed references from "default-set" to "default-filter" to match cargo-nextest changes.

cargo-nextest 0.9.77

28 Aug 21:35
Compare
Choose a tag to compare

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.

nextest-runner 0.59.0

25 Aug 20:13
Compare
Choose a tag to compare

nextest-metadata 0.11.3

25 Aug 20:10
Compare
Choose a tag to compare

Changed

  • NextestExitCode::INVALID_FILTER_EXPRESSION has been renamed to
    NextestExitCode::INVALID_FILTERSET. The old name is kept around as a deprecated alias -- it will
    be removed in the next major version.

nextest-filtering 0.11.0

25 Aug 20:12
Compare
Choose a tag to compare

Changed

  • Types renamed from FilteringExpr to Filterset.