You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Antoine Tran (JIRA)" <ji...@apache.org> on 2017/03/24 14:37:41 UTC
[jira] [Commented] (SUREFIRE-1346) surefire-reports overwrite each
other when using reuseForks=false
[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940464#comment-15940464 ]
Antoine Tran commented on SUREFIRE-1346:
----------------------------------------
None of the duplicated issue are in open state.
> surefire-reports overwrite each other when using reuseForks=false
> -----------------------------------------------------------------
>
> Key: SUREFIRE-1346
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1346
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking, TestNG support
> Affects Versions: 2.19.1
> Reporter: Antoine Tran
>
> In a Maven project with the setting "<reuseForks>false</reuseForks>" and TestNg, the file testng-result.xml gets overwritten by the last test.
> I somehow understand why it is difficult to avoid this by design of fork, but the proper solution, as suggested by SUREFIRE-1018 or SUREFIRE-446, is to use the individual TEST-[className].xml files.
> However, if I use a Jenkins plugin like testng, I cannot make him ingest these files, as they do not have the same structure as testng-result.xml. This is a bug of testng, rather than the Jenkins plugin testng. Couldn't we make testng-result-[className].xml, for each test, with the testng-result.xml structure? Otherwise, the Jenkins plugin https://wiki.jenkins-ci.org/display/JENKINS/testng-plugin is completely not usable.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)