Closed alfaix closed 2 months ago
Hey :wave:
rustaceanvim gets the test positions from rust-analyzer and isn't aware of different test frameworks. So I'm afraid this can only be solved upstream, in rust-analyzer.
Regarding more reliable parsing of the test results: That will be solved when #462 has been implemented. I don't know when I'll have time for that, but it is on my radar.
Have you read the docs and searched existing issues?
Neovim version (nvim -v)
v0.11.0-dev-7b7c95dac
Operating system/version
Ubuntu 22.04
Output of :checkhealth rustaceanvim
How to reproduce the issue
Expected behaviour
Test cases should be treated as if they are separate tests:
I think this comes from the overlapping (or empty) text range for test cases.
Actual behaviour
The cases are treated as if it's just one test by the main-editor UI. Examples: running all tests (shows checkmark next to the test, should be a cross) running nearest test when cursor is at a case line runs the last test
I understand this is a minor issue, but I usually don't use the summary window (just run file-run nearest), and I just spent ~15 minutes trying to understand why a test was failing assuming another test I ran before was successful, but turns out that test never ran at all. I think in neotest this should be doable if the range for a test supplied is limited to one line (the #[case] line), or just the #[case] statement in case they are on the same line.
The minimal config used to reproduce this issue.