fix: fix junit 6 support

[wenytang-ms]

fix issue #1837

[wenytang-ms]

Root Cause Analysis
The bug occurs in the findTestItemsInTypeBinding method of TestSearchUtils.java. This method is called when a test file is opened or changed (via the file watcher triggering findTestTypesAndMethods).

[wenytang-ms]

OpenFile→ findTestTypesAndMethods()
→ TestKindProvider return [JUnit6]
→ Mapping to [JUnit6TestSearcher]
→ findTestItemsInTypeBinding()
→ isAccessibleClass filter JUnit6TestSearcher → searchers = []
→ No test cases found → into else
→ JUNIT5_TEST_SEARCHER.isTestClass() = true
→ testKind is hardcoded to JUnit5 ← BUG
→ test item take testKind=JUnit5 and set into dataCache

User run test cases → mapTestItemsByKind() from dataCache read testKind=JUnit5
→ testContext.kind = JUnit5
→ send JSON { testKind: 0 } to Java Extension
→ JUnitLaunchUtils Mapping to JUNIT5_LOADER
→ preLaunchCheck check JUnit 5 jar → not found → error

[Copilot]

Pull request overview

Fixes issue #1837 where JUnit 6 projects are incorrectly handled as JUnit 5 (leading to misleading “JUnit 5 … build path” errors), by improving JUnit 6 kind selection and discovery behavior.

Changes:

• Updated bundled JUnit 5/Platform jar versions used by the extension.
• Improved test kind resolution to correctly label items as JUnit 6 in cases where JUnit 5 and JUnit 6 annotations overlap.
• Added a JDT accessibility-check fallback to avoid incorrectly rejecting valid JUnit 6 @Nested test classes.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
package.json	Updates the extension’s bundled JUnit jars used on the server side.
java-extension/com.microsoft.java.test.plugin/src/main/java/com/microsoft/java/test/plugin/util/TestSearchUtils.java	Adjusts test discovery/kind assignment and accessibility checks for JUnit 6 compatibility.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.