rust-lang / rust-lang/rust-analyzer
Show errors at a better location based on the backtrace in VS Code's test integration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Using the new test explorer, write a test that panics, and notice the failure message is associated with the location of the test, which can move the developer away from the context of what failed.
Instead, the extension could attempt to parse the backtrace from Rust and associate the location of the failure message with the first location it sees within the range of the test case. This doesn't work in all cases (notably with async tests) but should otherwise provide a nice experience.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the VS Code test integration and how Rust panic backtraces are reported. Check how the test explorer currently associates failures with test locations, then assess parsing the first backtrace location within the test case range. Done means applicable failures point to that location while async cases remain supported as far as the issue allows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- devtools, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100