Selecting one test from a parametrized test, reruns all tests, but the result is filtered #1657

Activity

1. Sheng Chen (jdneo)

   added

   bug

   on Feb 1, 2024
2. github-actions commented on Nov 12, 2025

   

   github-actionsBot

   on Nov 12, 2025 – with GitHub Actions

   More actions

   Hi Tamas (@smil2k), 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.

   This is a known issue tracked here:

   • Bug: Re-running multiple invocations of parameterized tests from different methods may run the complete classes instead
     Bug: Re-running multiple invocations of parameterized tests from different methods may run the complete classes instead #1411

   Suggested workarounds:

   • Update the VS Code Java Test Runner extension to the latest version (>= v0.35) which includes the fix from PR feat: re-run single JUnit5 parameterized test invocation via uniqueId #1407
     feat: re-run single JUnit5 parameterized test invocation via uniqueId #1407
   • In the Test Explorer, click the Run/Debug icon next to the specific parameter node instead of selecting multiple children at once.
   • Avoid selecting all methods or parameter sets of a class when re-running tests; pick only the exact invocation you need.

   Other references with low confidence

   • Re-run a single invocation of JUnit5 Parameterized Tests
     Feature request describing rerunning a single invocation in Test Explorer
     Re-run a single invocation of JUnit5 Parameterized Tests #1408
   • Stop raising an error when re-running all invocations of a JUnit5 test method
     Discussion around running all invocations, not directly this bug
     Stop raising an error when re-running all invocations of a JUnit5 test method #1416 (comment)

   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!
3. github-actions

   added

   ai-triaged

   duplicate

   junit

   test-execution

   on Nov 12, 2025
4. github-actions

   closed this as not plannedon Nov 12, 2025
5. smil2k commented on Nov 13, 2025

   

   Tamas (smil2k)

   on Nov 13, 2025

   Author

   More actions

   Dear robot!

   This is a different bug, my vscode is up-to-date:

   Identifier vscjava.vscode-java-test
   Version 0.43.2

   The problem is not necessarily in vscode, I've seen such issues in js also.