feat: route real test program output to Test Results

[wenytang-ms]

Problem

Running a test with the Java Test Runner splits output across two disconnected surfaces:

• Program and debug output is delivered by java-debug as standard DAP output events, which normally appear only in the Debug Console.
• Test results are driven by the runner's socket protocol and displayed in Test Results.

The runner also echoed raw JUnit/TestNG control frames into Test Results, producing protocol noise such as %TESTS, %TESTE, and TestNG JSON frames instead of useful user-facing output.

See eclipse-jdtls/eclipse.jdt.ls#3834 for the broader discussion.

Change

• Mirror Debug Console output in Test Results. Attach a DebugAdapterTracker to the test debug session and forward all non-telemetry DAP output events through TestRun.appendOutput.
• Keep output at the test-run level. DAP output is process-level and has no reliable test identifier, so it is not guessed onto individual test cases.
• Correlate the exact debug session. Add a unique internal run ID to the launch configuration instead of matching sessions by display name.
• Remove control protocol noise. JUnit no longer appends raw socket frames, and TestNG no longer echoes its JSON frames.
• Preserve structured diagnostics. Test states, stack traces, and expected-vs-actual values continue to use the Testing API. TestNG runner-level error frames are surfaced as structured test errors.

This requires no changes to java-debug; it consumes the standard DAP events already emitted by the debug session.

Notes / limitations

• TestRun.appendOutput is an uncategorized stream, so stdout, stderr, and console color separation is not preserved.
• The Debug Console remains unchanged and continues to display the categorized output.

Validation

• TypeScript compilation: clean
• ESLint on changed source files: clean
• Integration tests: 135 passing

[Copilot]

Pull request overview

This PR improves the VS Code Java Test experience by routing real program/debug output into Test Results (in addition to the Debug Console) and by suppressing runner-protocol “noise” previously echoed into Test Results.

Changes:

• Adds a DebugAdapterTracker for the specific Java test debug session (correlated via an internal run UUID) and forwards non-telemetry DAP output events to TestRun.appendOutput.
• Stops echoing raw control/protocol frames into Test Results for JUnit and TestNG; preserves structured diagnostics via the Testing API.
• Adds/updates tests to validate DAP-output forwarding and TestNG runner-error handling / control-frame ignoring.

Reviewed changes

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

Show a summary per file

File	Description
test/suite/TestNGAnalyzer.test.ts	New unit tests for TestNG analyzer: structured runner error surfacing and ignoring control frames without test attributes.
test/suite/baseRunner.test.ts	Adds unit tests covering BaseRunner.handleDebugAdapterMessage forwarding behavior and telemetry filtering.
src/runners/testngRunner/TestNGRunnerResultAnalyzer.ts	Stops echoing raw TestNG frames; ignores control frames without test identifiers; surfaces runner-level error frames as structured test errors; makes duration parsing resilient.
src/runners/junitRunner/JUnitRunnerResultAnalyzer.ts	Removes echoing of raw JUnit socket lines into Test Results (protocol-only stream), relying on structured messages instead.
src/runners/baseRunner/BaseRunner.ts	Correlates the correct debug session via internal run ID, attaches a tracker, and mirrors non-telemetry DAP output events into Test Results with CRLF normalization.

---

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

[wenytang-ms]