[
http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich updated SUREFIRE-377:
----------------------------------
Fix Version/s: (was: 2.4)
IMO, this problem is probably too hard to be worth solving. See the mailing
list archive thread here:
http://mail-archives.apache.org/mod_mbox/maven-surefire-dev/200711.mbox/[EMAIL
PROTECTED]
http://tinyurl.com/32745g
Alex suggested a good way to tell the different between JUnit and TestNG runs,
but trying to dynamically construct multiple test runs from two arrays of
classes that don't clobber each other when you go to run them is harder than it
has any right to be.
> When JUnit and TestNG tests are in same project, only one set gets run
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-377
> URL: http://jira.codehaus.org/browse/SUREFIRE-377
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.4
> Reporter: Dan Fabulich
> Attachments: testng-junit-together.zip
>
>
> The attached Maven project has two tests: one JUnit test and one TestNG test.
> According to the documentation, in this case TestNG should run both tests.
> Run "mvn test". Only the TestNG test will run. If you modify the pom to set
> the property "junit=true", only the JUnit test will run.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.4-SNAPSHOT</version>
> <configuration>
> <properties>
> <property>
> <name>junit</name>
> <value>true</value>
> </property>
> </properties>
> </plugin>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
