microsoft / microsoft/vscode-java-test
"Go to Test" for nested/inner Tests in a JUnit Test Suite
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 340
- Forks
- 173
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 18
Description
I would like to request a feature/fix for the empty context menu for JUnit Tests under a (Custom)TestSuite. At least I would need the "Go to Test" functionality (or a double-click on the Test) as you can see in the screenshots below.
See also original issue: https://github.com/microsoft/vscode-java-test/issues/647
After running a JUnit Test Suite, the executed Tests under the Suite are shown, but it's not possible to jump to a Test (you can only hide Tests):

When you restart VS Code, the nested Tests are not even shown (maybe this is by design?):

For Tests without a Suite the context menu has an "Go to Test" entry:

Here you can find my example project: https://github.com/steinerthomas/junit-suite-example
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 reproducing the nested-test behavior in the linked junit-suite-example project after running a JUnit suite in VS Code. Compare the nested test actions with the context menu for a standalone test, and review the original issue 647 for prior discussion; done means nested tests support the requested navigation action and remain usable after restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100