The release adds native cargo-nextest integration with progress reporting and structured results in the Test tool window. That means developers can run and monitor Nextest sessions without leaving the IDE. JetBrains says the goal is to refine core workflows and reduce friction in routine Rust testing.
This should help teams that work in large Rust workspaces and want faster feedback loops. Instead of bouncing between the terminal and the IDE, the test lifecycle is visible in one place. That matters because testing speed and visibility often have a direct impact on developer throughput and confidence.
If your Rust projects already use Nextest, upgrade RustRover and test the native integration in one workspace before rolling it out widely. Validate that the IDE reporting matches your team’s expectations for test output and failures. The biggest value comes from keeping the workflow inside the editor while still getting Nextest’s speed gains.
Read Original Post →