[ 
https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792470#comment-17792470
 ] 

Alexander Kriegisch commented on SUREFIRE-2219:
-----------------------------------------------

[~michael-o]: One example is [this Reddit 
thread|https://www.reddit.com/r/javahelp/comments/uo1vz6/can_surefire_reports_including_logging_systemout/].
 Two years ago, [~khmarbaise] replied to it, recommending to open an issue for 
it, which I just did. 😉

Other posts revolve around workarounds like using 
[{{redirectTestOutputToFile}}|https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirecttestoutputtofile],
 which retains the information, but does not embed it into the Surefire report. 
There also seems to be an [option {{keepLongStdio}} in the Jenkins JUnit 
plugin|https://www.jenkins.io/doc/pipeline/steps/junit/#:~:text=keepLongStdio%20%3A%20boolean%20%28optional%29]
 to retain the output.

> Option to include stdOut/stdErr console logs into test report
> -------------------------------------------------------------
>
>                 Key: SUREFIRE-2219
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2219
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Maven Surefire Report Plugin
>    Affects Versions: 3.2.2
>            Reporter: Alexander Kriegisch
>            Priority: Major
>         Attachments: image-2023-12-02-11-16-11-109.png
>
>
> Surefire report XML includes tags capturing console logs, e.g. 
> {{testsuite/testcase/system-err}}:
>  !image-2023-12-02-11-16-11-109.png! 
> As a report reader, I want to see the stdOut/stdErr console logs per test 
> case in the HTML report, ideally in a monotype font to easily be able to read 
> stack traces.
> This requirement has been discussed online a lot, e.g. on Stack Overflow or 
> Reddit. I wonder why such a feature is missing. The HTML report basically 
> being an XML transformation from the surefire report, it should not be super 
> complicated to implement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to