Skip to content

JUnit 5 @Suite classes do not update status icons in Test Explorer #1828

Closed
Closed
JUnit 5 @Suite classes do not update status icons in Test Explorer#1828
Assignees
wenytang-ms
Labels
ai-triagedjunitneeds-reproductiontest-reporting

Description

@Biyakuga
Biyakuga Higashiri (Biyakuga)
opened on Jan 19, 2026

Description

When running a JUnit 5 Test Suite (using Matt (@suite) and @SelectPackages), the tests execute successfully, but the VS Code Test Explorer UI and Test Results panel do not update to show the "Passed" state (green checkmarks). The Suite class often remains in a "running" or "unknown" state visually or does not expand to show the tests being run, even though the Output console confirms execution.

Reproduce

Steps to reproduce the behavior:

  1. Create a simple JUnit 5 project with junit-platform-suite.
  2. Create a Suite class:
    @Suite @SelectPackages("com.example.tests") public class MyTestSuite { }
  3. Click the "Run Test" (Play icon) next to the MyTestSuite class in the Test Explorer.
  4. Observe that the tests run (output is generated), but the UI does not show checkmarks for the Suite.

Expected behavior

The Test Explorer should visually reflect that the Suite and its contained tests have passed (green checkmarks), similar to how individual test classes behave.

Current behavior

  • The tests execute (verified via console output).
  • The Test Explorer sidebar does not show checkmarks for the Suite.
  • The Output tab ("Test Output") shows raw Eclipse protocol messages (e.g., %TSTTREE, %TESTS, %TESTE) instead of a clean summary or UI update.

Image for visualization:

As you can see in the Test Results Panel" no checkmark ✅ icon or fail icon only grey arrow the same behavior happens in the "Test Explorer Sidebar"
Image

Sample Output (Raw Protocol seen in Output tab)
%TSTTREE54,com.example.MyTest,true,2,false,3,MyTest,,[engine:junit-jupiter]/[class:com.example.MyTest] %TESTS 61,shouldDoSomething(com.example.MyTest) %TESTE 61,shouldDoSomething(com.example.MyTest)

Environment

VS Code Version 1.108.1
Windows 11 latest stable version
Java official Microsoft Pack latest version
JUnit Jupiter (Aggregator) version 5.14.2
Junit Platform Suite (Aggregator) version 1.14.2

Activity

  1. github-actions commented on Jan 19, 2026

    @github-actions
    github-actionsBot
    on Jan 19, 2026 – with GitHub Actions

    Hi Biyakuga Higashiri (@Biyakuga), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

    The VS Code Java Test Runner currently doesn’t fully update Test Explorer status for JUnit 5 Matt (@suite) classes. You can try the following workarounds:

    • Add the JUnit Platform Suite Engine to your classpath so the suite container reports results properly: 
      <dependency>
  <groupId>org.junit.platform</groupId>
  <artifactId>junit-platform-suite-engine</artifactId>
  <version>1.14.2</version>
</dependency>
    • Update to the latest Test Runner for Java extension in VS Code (check for updates in the Extensions view).
    • Enable debug logging for the test runner to inspect protocol messages: 
      // settings.json
"java.test.logLevel": "debug"
    • If the issue persists after the above, please file a new bug on the Java Test Runner repo: https://github.com/microsoft/vscode-java-test/issues/new?template=bug_report.md

    The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

  2. github-actions
    added
    ai-triaged
    bug
    junit
    test-reporting
    on Jan 19, 2026
  3. Biyakuga Higashiri (Biyakuga)
    closed this as completedon Jan 19, 2026
  4. Biyakuga Higashiri (Biyakuga)
    reopened this on Jan 19, 2026

  5. Biyakuga commented on Jan 19, 2026

    @Biyakuga
    Biyakuga Higashiri (Biyakuga)
    on Jan 19, 2026
    Author

    I mistakenly closed the issue, but the problem is still occurring. I have verified this across several environments and observed the same result. There is no indication of whether the test suite has passed or failed.

    In IntelliJ, however, it displays a checkmark (✅).

  6. Biyakuga commented on Feb 16, 2026

    @Biyakuga
    Biyakuga Higashiri (Biyakuga)
    on Feb 16, 2026
    Author

    Sheng Chen (@jdneo)

    Would you mind taking a look at this issue when you have a chance?
    I’m currently blocked by this behavior. In my project, I have around 50 test classes organized across different packages, and I rely on a JUnit 5 Suite (Matt (@suite) + @SelectPackages) to run them together. Since the Test Explorer UI does not reflect the pass/fail status of the Suite (no green/red indicators or structured results), I’m forced to run the test classes individually to understand whether new changes have broken anything.

    This significantly slows down my workflow, especially when adding new features, because I don’t get clear visual or contextual feedback about which tests passed or failed and why.

    Any guidance or workaround would be greatly appreciated. Thank you!

  7. wenytang-ms commented on Mar 6, 2026

    @wenytang-ms
    wenyt (wenytang-ms)
    on Mar 6, 2026
    Contributor

    Hi Biyakuga Higashiri (@Biyakuga) we’ve released a prerelease version 0.44.2026030602 of test-runner-for-java, which fixes the issue you reported. Please install this version together with the latest prerelease of vscode-gradle and help verify the fix.

  8. wenyt (wenytang-ms)
    self-assigned this
    on Mar 6, 2026

  9. Biyakuga commented on Mar 6, 2026

    @Biyakuga
    Biyakuga Higashiri (Biyakuga)
    on Mar 6, 2026
    Author

    Hi @Biyakuga we’ve released a prerelease version 0.44.2026030602 of test-runner-for-java, which fixes the issue you reported. Please install this version together with the latest prerelease of vscode-gradle and help verify the fix.

    Thank you. I will make sure to test it once it is fully released to the stable version, as my company does not allow installing pre-release versions of software or extensions.

  10. wenyt (wenytang-ms)
    added
    needs-reproduction
    and removed
    bug
    on Mar 9, 2026

  11. wenytang-ms commented on Apr 15, 2026

    @wenytang-ms
    wenyt (wenytang-ms)
    on Apr 15, 2026
    Contributor

    Biyakuga Higashiri (@Biyakuga)
    we shipped the stable version as 0.45.0 to test-runner, please help verify this issue. thanks

  12. wenytang-ms commented on Apr 20, 2026

    @wenytang-ms
    wenyt (wenytang-ms)
    on Apr 20, 2026
    Contributor

    Biyakuga Higashiri (@Biyakuga) close this this issue since too long no response, please feel free to reopen this issue once repro with target version.

  13. wenyt (wenytang-ms)
    closed this as completedon Apr 20, 2026

  14. Biyakuga commented on May 15, 2026

    @Biyakuga
    Biyakuga Higashiri (Biyakuga)
    on May 15, 2026
    Author

    @Biyakuga we shipped the stable version as 0.45.0 to test-runner, please help verify this issue. thanks

    Sorry, I was on a long vacation. I would like to inform you that the issue has been fixed.
    By the way, it would be really helpful if GitHub implemented a notification area similar to YouTube’s, so when someone comments or replies to me, it’s easier to notice and keep track of updates.

  15. wenytang-ms commented on May 18, 2026

    @wenytang-ms
    wenyt (wenytang-ms)
    on May 18, 2026
    Contributor

    In fact, as the creator of this GitHub issue, you are already subscribed to all notifications related to it; it is possible that you have filtered out GitHub notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ai-triagedjunitneeds-reproductiontest-reporting

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions