[jira] [Commented] (SUREFIRE-1230) Issue with config parameter 'redirectTestOutputToFile' when running cucumber parallel tests

["Tibor Digana (JIRA)" <ji...@apache.org>]

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

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

[~mpalki]
Sorry for late reply. Can you check it out with no forks (forkCount=0, forkMode=never)?
If it happens only with forking, debug the events received by ForkCLient.java.
If it happens with in-process run, then the bug has to do with Surefire's RunListener.java and subtypes.

> 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
>         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)