redhat-developer / redhat-developer/vscode-java
Support debug on SpyBeans
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Can't debug a class annotated with SpyBean annotation, this makes hard to debug testes because I need to comment the annotation and all the verify statements.
I uploaded a project as sample, if you uncomment the SpyBean annotation you will be able to debug it.
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
Begin with the linked sample-project.zip and reproduce the problem by uncommenting the SpyBean annotation, then try debugging the affected test. Done means the class can be debugged without commenting out SpyBean or the verify statements; the issue names no source file or test entry point, so tracing the extension's Java debugging path will be necessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, typescript
- Domain
- developer-experience, testing, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100