JUnit5 DynamicContainer are not working again (regression) #1792

Activity

1. github-actions commented on Sep 29, 2025

   

   github-actionsbot

   on Sep 29, 2025 – with GitHub Actions

   More actions

   Hi Massimo Santini (@mapio), 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.

   Suggestions

   • This is a known regression of issue JUnit5 DynamicContainer are not working #1617. Please monitor that issue for a fix in the next Test Runner for Java release:

     • JUnit5 DynamicContainer are not working #1617

   • Workarounds until it’s fixed:

     • Run the factory via the root container (right-click > Run All) instead of the individual DynamicContainer.
     • Use the Gradle or Maven CLI (./gradlew test or mvn test) to see failure details in the terminal.
     • Enable verbose test logging in VS Code settings:

       "java.test.log.level": "verbose"

   • If you can share verbose logs or a minimal repro, please add them to JUnit5 DynamicContainer are not working #1617 to help the investigation.

   Other references with low confidence

   Related: DynamicTest launch via sidebar

   • JUnit Jupiter DynamicContainer and DynamicTest launching from the test side bar does not work (JUnit Jupiter DynamicContainer and DynamicTest launching from the test side bar does not work #1643) — tests show in the tree but clicking Run/Debug on an individual dynamic test fails: JUnit Jupiter DynamicContainer and DynamicTest launching from the test side bar does not work #1643

   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

   duplicate

   junit

   test-reporting

   high-priority

   investigating

   on Sep 29, 2025
3. mapio commented on Sep 30, 2025

   

   Massimo Santini (mapio)

   on Sep 30, 2025

   Author

   More actions

   To help you reproduce the issue: this is the output of the insiders version

   

   obtained with the included code

   bugrep.zip

   As you can see, the TEST RESULTS panel reports all the tests, but the TESTING side panel lists only the name of the method generating the container, not the single tests (as it were doing before I upgraded to Java 25).
4. mapio commented on Sep 30, 2025

   

   Massimo Santini (mapio)

   on Sep 30, 2025

   Author

   More actions

   The problem is solved if using "Delegate to Gradle" in the testing side panel.