Feature Req: Compound config support.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, java, typescript, vscode
- Domain
- developer-experience, testing
Research direction
Start by reviewing how java.test.config is specified outside launch.json and how the Java test configuration is generated for a debug action. Compare that behavior with VS Code compound configurations in launch.json; done should mean a Java test and a GDB C++ debugging instance can be launched together for JNI debugging.
Written by the indexing model from the issue text.
Description
Are there any plans to add support for compound configurations (i.e. as the rest of vscode can do through defining compound configurations in launch.json)? Use case is JNI interfaces; want to launch a java test, and simultaneously launch a GDB C++ debugging instance that attaches to java to allow debugging when we reach C++ code.
Right now the specification of java.test.config outside of launch.json and the automated generation of the java side test config (to correspond to the method that we hit debug on) means we can't define a compound debugging config.
Obvious workaround right now is to have multiple instances of vscode running, and manually attach after launching and hitting a breakpoint on the java side, but would be immensely useful to have this natively supported in vscode-java-test.
- Dominant language
- TypeScript
- Stars
- 340
- Forks
- 173
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 18
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.
More from microsoft/vscode-java-test
-
ai-triaged bug high-priority investigating junit maven test-discovery
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-java-test#1915 · 2 comments ·
-
ai-triaged bug investigating junit test-discovery test-execution
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/vscode-java-test#1897 · 1 comment ·
-
ai-triaged bug gradle high-priority test-execution
microsoft/vscode-java-test#1880 · 2 comments · 1 assignee ·
-
ai-triaged gradle junit test-execution ux
microsoft/vscode-java-test#1878 · 3 comments · 1 assignee ·
-
ai-triaged enhancement junit low-priority test-execution ui
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-java-test#1836 · 4 comments ·
All issues in microsoft/vscode-java-test
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·