[
https://jira.codehaus.org/browse/SUREFIRE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-769.
---------------------------------
Resolution: Not A Bug
You can run separate executions instead: (default-test) and (t1)
{code}
<build>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.18.1</version>
<executions>
<execution>
<id>t1</id>
<phase>test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<enableAssertions>false</enableAssertions>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
> run test more than once with different context at each run
> ----------------------------------------------------------
>
> Key: SUREFIRE-769
> URL: https://jira.codehaus.org/browse/SUREFIRE-769
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Affects Versions: 2.9
> Environment: all
> Reporter: luc peuvrier
> Attachments: pied.gif
>
>
> I need to run tests twice: one with -ea jvm argument, the second with -da jvm
> argument.
> I will also need to test with and whithout a java agent.
> About asserion enabled mode" of the jvm I dicovered a bug that make test pass
> if assertion enabled and fail id assertion disabled.
> The feature proposal is firstly to detect such bugs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
