nextest-runner 0.3.0

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

cargo-nextest 0.9.8

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

nextest-runner 0.2.1

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

nextest-runner 0.2.0

Added

• Support for target runners.

cargo-nextest 0.9.7

Fixed

• If parsing target runner configuration fails, warn and proceed without a target runner rather than erroring out.

Known issues

• Parsing an array of strings for the target runner currently fails: #73. A fix is being worked on in #75.

cargo-nextest 0.9.6

Added

• Support Cargo configuration for target runners.

nextest-runner 0.1.2

Added

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

cargo-nextest 0.9.5

Fixed

• Updated nextest-runner to 0.1.2, fixing cyan coloring of module paths (#52).

cargo-nextest 0.9.4

The big new change is that release binaries are now available! Head over to Pre-built binaries for more.

Added

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

Fixed

• While querying binaries to list tests, lines ending with ": benchmark" will now be ignored (#46).

cargo-nextest 0.9.5-rc.2

(Temporary release) test out binary releases once again.