enhancement: syncronization with maven
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, testing
Research direction
Start by reviewing the test runner settings, the Maven pom, and the Surefire plugin configuration described in the issue. Define how synchronization should handle Maven project variables, pom properties, and Surefire include/exclude settings; done means the proposed sync setting produces comparable test-runner behavior without duplicate configuration.
Written by the indexing model from the issue text.
Description
The use case for me is that essentially I run my testcases in maven
with surefire plugin.
Only if something goes wrong I switch to the test runner to analyze the details.
Then I switch back.
Currently, I have to configure both, the test runner in settings, and maven in the pom.
It would be some help if I could use the variables available in maven pom.
At least the ones available for maven projects,
better in addition those defined in the properties section in the pom.
Even better if I just can use the config of the surefire plugin.
Even helpful it would be if the settings in both worlds are comparable.
So I miss a way to include and exclude tests in test runner as provided by the surefire plugin.
Concrete suggestion: setting to syncronize with surefire
"java.test.conig": {
"syncSurefire": "true" % with default false
}
- Dominant language
- TypeScript
- Stars
- 340
- Forks
- 173
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 17
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 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 ·
-
ai-triaged enhancement gradle investigating junit low-priority test-reporting
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-java-test#1824 · 1 comment ·
All issues in microsoft/vscode-java-test
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·