microsoft / microsoft/vscode-java-debug
Feature request: set breakpoint on assert fail
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
Feature request: set breakpoint on assert fail
Currently, when a Java assert fails, a stack trace is written to the terminal and the application ends. We know which assertion failed, but the application state is lost making it impossible to troubleshoot.
It would be nice to set this parameter in settings.json
"java.debug.breakOnAssertFail": true
Once this parameter has been implemented, when an assertion fails, the breakpoint pauses the application at the line where the assert failed, preserving the application state and allowing troubleshooting to proceed.
Eclipse has this feature; VSCode should too.
Thanks!
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
The issue names settings.json and Java assertion failures but does not identify repository files or tests. Start by locating the assertion-failure handling and the setting registration, then trace how debugger pauses are requested. Done means the setting enables pausing at the failed assertion while preserving application state, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100