[
https://issues.apache.org/jira/browse/SUREFIRE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071573#comment-16071573
]
Elias Balasis commented on SUREFIRE-875:
----------------------------------------
Yes, that's exactly what I do but manually in my custom listener, by moving and
renaming testng-results.xml of previous execution.
I am thinking of a change in both Surefire (an extra pass-through TestNG
instruction) and TestNG (the extra instruction)
> testng-results contains only last suite execute in forkmode = always
> --------------------------------------------------------------------
>
> Key: SUREFIRE-875
> URL: https://issues.apache.org/jira/browse/SUREFIRE-875
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 2.12
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
> OS name: "linux", version: "3.0.0-20-generic", arch: "amd64", family: "unix"
> Reporter: Michał Kalisz
> Attachments: misiu.test-0.0.1-SNAPSHOT-test-sources.jar, pom.xml
>
>
> Every fork creates new testng-results.xml by replacing previous one.
> If there are two tests class - to suite will be created and only last one
> will be visible in testng-results.xml.
> In attached project:
> Two test classes:
> SimpleIT, CopyOfCopyOfSimpleIT
> running: mvn verify
> Generates two sites:
> Running pl.misiu.CopyOfCopyOfSimpleIT
> Configuring TestNG with:
> org.apache.maven.surefire.testng.conf.TestNGMapConfigurator@771c8a71
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.362 sec
> Running pl.misiu.SimpleIT
> Configuring TestNG with:
> org.apache.maven.surefire.testng.conf.TestNGMapConfigurator@72c53dce
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.326 sec
> In target/failsafe-reports/testng-results.xml
> there is only one test SimpleIT (the last execute site)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
