vscode-rust-test-adapter
vscode-rust-test-adapter copied to clipboard
swellaby
Capture test failure details
Capture the output of failed tests make it available on each test node in the explorer
This is still the next major focus area, we just need to finish #14 ASAP
My guess is that one depends on #43. You cannot split stdout in multi thread tests without leverage on cargo json output format.
My guess is that one depends on #43. You cannot split stdout in multi thread tests without leverage on cargo json output format.
I'm still confident that we can support extracting test failure content from the default pretty format, though json would obviously be far, far easier! I'm hoping that the json format option will be stabilized soon
--message-format json should be stable https://doc.rust-lang.org/cargo/commands/cargo-test.html
I missed something?
You need to use the --format option that's passed to the test binary, which is different than --message-format used with cargo and subcommands.
cargo test -- --format json, and json is not yet stabilized there.
AFAIK, cargo test --message-format json does not actually emit the test results in json format
Sorry... I saw what I missed...
cargo test -- -Z unstable-options --format=json
AFAIK, cargo test --message-format json does not actually emit the test results in json format Right
My falut sorry.
Anyway on intellj they already use it and maybe it will never change... Anyway I wasn't able to find the ticket that track stabilization :(
No worries! We're (tentatively) planning on implementing this with the default/stable pretty format to ensure we can do the basics with stable-only options, and then shifting focus to the json format