You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bill Wallace (JIRA)" <ji...@codehaus.org> on 2007/02/23 22:24:11 UTC
[jira] Commented: (SUREFIRE-169) No tests detected when both TestNG
and JUnit in classpath
[ http://jira.codehaus.org/browse/SUREFIRE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88393 ]
Bill Wallace commented on SUREFIRE-169:
---------------------------------------
An initial change to just allow the type of test suites to run would be very helpful - eg
JUnit 4
POJO
JUnit 3
TestNG
as a plugin configuration.
Then, later on it would be nice if all tests just run - whether JUnit or TestNG, without duplications. It doesn't much matter which system they run in, as long as the tests get run.
> No tests detected when both TestNG and JUnit in classpath
> ---------------------------------------------------------
>
> Key: SUREFIRE-169
> URL: http://jira.codehaus.org/browse/SUREFIRE-169
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, JUnit 3.x support, TestNG support
> Affects Versions: 2.0 (2.2 plugin)
> Environment: Linux, JDK1.5
> Reporter: Jim Crossley
> Fix For: 2.4
>
>
> I have a multi-module project where testng is declared as a dep in the parent and a subproject declares junit as a dep. When I invoke 'mvn test' in the subproject, surefire doesn't detect any tests to run. If I simply remove the testng dep from the parent, the tests run fine.
--
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