Skip to content

Commit 578b737

Browse files
misrasaurabh1claude
andcommitted
fix: enable stdout capture in JUnit Console Launcher XML reports
Configure JUnit Console Launcher to capture stdout/stderr in XML reports: - Add --config=junit.platform.output.capture.stdout=true - Add --config=junit.platform.output.capture.stderr=true - Change --details=verbose to --details=none to avoid duplicate output This ensures timing markers are properly captured in the JUnit XML's <system-out> element, eliminating the need to rely on subprocess stdout fallback for parsing timing markers. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 051d1b6 commit 578b737

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

codeflash/languages/java/test_runner.py

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -422,7 +422,13 @@ def _run_tests_direct(
422422
"org.junit.platform.console.ConsoleLauncher",
423423
"--disable-banner",
424424
"--disable-ansi-colors",
425-
"--details=verbose",
425+
# Use 'none' details to avoid duplicate output
426+
# Timing markers are captured in XML via stdout capture config
427+
"--details=none",
428+
# Enable stdout/stderr capture in XML reports
429+
# This ensures timing markers are included in the XML system-out element
430+
"--config=junit.platform.output.capture.stdout=true",
431+
"--config=junit.platform.output.capture.stderr=true",
426432
]
427433

428434
# Add reports directory if specified (for XML output)

0 commit comments

Comments
 (0)