You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: route real test program output to Test Results (#1887)
* feat: route real test program output to Test Results
The debuggee's stdout/stderr are delivered by java-debug as standard DAP
`output` events, which by default only surface in the Debug Console. This
splits program output (Debug Console) from test results (Test Results view)
across two separate surfaces, and the runner previously echoed the raw
JUnit/TestNG control protocol frames to Test Results as noise.
- Attach a DebugAdapterTracker to the test's own debug session and forward
its DAP `output` events into the Test Results view (BaseRunner).
- Stop echoing the socket control protocol to Test Results: JUnit no longer
appends every raw line, and TestNG no longer echoes its JSON frames.
- Attribute forwarded output to the running test when exactly one test is
executing; fall back to run-level output when idle or when several tests
run in parallel (attribution would only be a guess).
* fix: route debug output at test run level
Correlate debug sessions with a unique launch marker, mirror non-telemetry DAP output at run level, and preserve structured TestNG runner errors while suppressing control protocol noise.
0 commit comments