Results not reported for JUnit 5 suites
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, typescript, vscode
- Domain
- devtools, testing-qa
Research direction
Unpack 1729-project.zip and compare TestSuiteForJUnit4.java with TestSuiteForJUnit5.java, starting with how each run is represented in the Test Results pane. Trace the test-result reporting path for both suites and verify the behavior by repeating the listed VS Code steps. Done means the JUnit 5 suite's test method is reported like the JUnit 4 suite.
Written by the indexing model from the issue text.
Description
Versions:
VSCode 1.92.2
Test Runner for Java 0.42.0
What happens:
When running a suite written with the JUnit 5 Jupiter API, the results of the test are not reported in the Test Results pane.
What was expected:
Test results from the suite should be reported in the same way as they are with suites written to the JUnit 4 API.
Steps to reproduce:
- Unzip the attached project.zip
- Launch Visual Studio Code for the project:
code project.code-workspace & - Browse to the class TestSuiteForJUnit4.java
- Click on the Play button to the left of the class declaration
- Observe that the test method is reported in the Test Results pane
- Browse to the class TestSuiteForJUnit5.java
- Click on the Play button to the left of the class declaration
- Observe that the test runs, but is not reported in the Test Results pane
Minimal example:
Screenshot:
- 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 ·