microsoft / microsoft/vscode-java-test

Results not reported for JUnit 5 suites

Open
#1,729 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged bug enhancement junit test-discovery
Dominant language
TypeScript
Stars
340
Forks
173
Avg merge
1d 19h
Merged PRs (30d)
18

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:
  1. Unzip the attached project.zip
  2. Launch Visual Studio Code for the project:
    code project.code-workspace &
  3. Browse to the class TestSuiteForJUnit4.java
  4. Click on the Play button to the left of the class declaration
  5. Observe that the test method is reported in the Test Results pane
  6. Browse to the class TestSuiteForJUnit5.java
  7. Click on the Play button to the left of the class declaration
  8. Observe that the test runs, but is not reported in the Test Results pane
Minimal example:

1729-project.zip

Screenshot:

1729-TestResultPane

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
java, typescript, vscode
Domain
devtools, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.