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

Tibor Digana commented on SUREFIRE-1230:
----------------------------------------

If the parameter {{redirectTestOutputToFile}} is set to {{true}} the logs 
should be dropped from console but appear in *.txt. The logic is a little bit 
more difficult because this depends on {{useFile}} as well.
If some Thread started by your test is logging to a console, we are not able to 
associate these logs with particular test class and therefore you won't be able 
to see the logs in {{TEST-MyTest.txt}} but you should be able to see it in 
{{TEST-null.txt}} together with logs from all tests having this problem.

> Issue with config parameter 'redirectTestOutputToFile' when running cucumber 
> parallel tests
> -------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1230
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1230
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.18.1
>            Reporter: Manoj Palki
>            Assignee: Tibor Digana
>         Attachments: cucumber_java_skeleton.tar.gz
>
>
> The config parameter redirectTestOutputToFile behaves differently based on 
> how parallelism is configured in the surefire plugin. 
> If the config is 
> <forkCount>2</forkCount>
> <reuseForks>false</reuseForks>
> <redirectTestOutputToFile>true</redirectTestOutputToFile>
> then the output from the tests is directed correctly to 'xxxtest-output.txt' 
> file. 
> However, if the config is
> <threadCount>2</threadCount>
> <parallel>classes</parallel>
> <redirectTestOutputToFile>true</redirectTestOutputToFile>
> then the output from the tests is partially directed to the 
> 'xxxtest-output.txt file and partially to stdout. 
> Also the output files have different names in two cases. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to