Replies: 4 comments 1 reply
-
|
Thanks -- honestly I'd been dreading this due to the complexity, but it wasn't too bad in the end. See #2985. |
Beta Was this translation helpful? Give feedback.
-
|
Could you try cargo-nextest 0.9.123-b.4? It has a new --cargo-message-format option. |
Beta Was this translation helpful? Give feedback.
-
|
Amazing, thank you! Really appreciate how quickly this was addressed, and hats off for tackling what looked like a nasty bit of complexity 🙌 |
Beta Was this translation helpful? Give feedback.
-
|
This is now out in cargo-nextest 0.9.123. By the way if and when RustRover ships nextest support, I'd love a PR to https://nexte.st/docs/integrations/. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
We're looking at
cargo nextestintegration into RustRover alongside withcargo test.One caveat is that
cargo nextestdoes not support Cargo's--message-formatoption (which works withcargo buildorcargo test --no-run).RustRover then uses the structured compiler output to show compilation errors/warnings in a structured way.
Screencast.from.2026-01-21.22-12-30.mp4
Any possibility of adding a similar feature? Don't confuse with an existing
--message-formatnextest option 😅More details
When running tests from RustRover, actually 2 commands are executed sequentially:
cargo test --no-run --message-format=json-diagnostic-rendered-ansicargo test -- --format=jsonThe first one compiles the binaries and produce compiler diagnostics (errors/warnings) if any.
The second one actually runs the tests using the default test framework.
In the case of
cargo nextest run, it looks like we can do the same trick, splitting the invocation into 2 commands:cargo nextest run --no-runcargo nextest run --message-format=libtest-json-plusThe problem here is that in the case of
cargo nextest run --no-run, there isn't an equivalent of Cargo's--message-format=json-diagnostic-rendered-ansi.We could workaround it by invoking
cargo test --no-run --message-format=json-diagnostic-rendered-ansiunder the hood instead ofcargo nextest run --no-run. But this option implies transforming the whole command line fromcargo nextesttocargo teston RustRover side, which would be too huge maintenance burdenBeta Was this translation helpful? Give feedback.
All reactions