VSCode Test Explorer - unit test execution is slow/problematic because they run at the workspace level not crate #17470
Labels
A-test-explorer
Issues related to the test explorer lsp extension and vscode test api
C-bug
Category: bug
Invoking a single unit test from the Test Explorer or keyboard shortcut will build the entire workspace and tests are processed in every workspace member which causes several problems:
mod tests :: test_arg_parsing
cargo test
completes in millisecondsExample test output trying to execute one unit test where rust-anlayzer tries to run a test in every single workspace member which I have anonymised as
<crate>
:@HKalbasi I can see this relates to your changes here:
#17056
I have a PR that behaves as I expect which is to run tests on the crate in which they are defined and not at the workspace root but I don't know if this will cause other issues.
The text was updated successfully, but these errors were encountered: