You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 23:29:21 UTC
[jira] Moved: (SUREFIRE-208) Surefire doesn't work if testng is in
the classpath and a suitexml isn't being used
[ http://jira.codehaus.org/browse/SUREFIRE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-117 to SUREFIRE-208:
-------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
Key: SUREFIRE-208 (was: MSUREFIRE-117)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Surefire doesn't work if testng is in the classpath and a suitexml isn't being used
> -----------------------------------------------------------------------------------
>
> Key: SUREFIRE-208
> URL: http://jira.codehaus.org/browse/SUREFIRE-208
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Jason Chaffee
> Assigned To: Brett Porter
> Attachments: patch.txt
>
>
> Bascially, not tests will be run. I was able to fix this in the latest surefire code, by changing this code in TestNGDirectoryTestSuite.java:
> try
> {
> Class junitClass = Class.forName( "junit.framework.Test" );
> xmlTest.setJUnit( testSet.getTestClass().isAssignableFrom( junitClass ) );
> }
> catch ( ClassNotFoundException e )
> {
> }
> to this code:
> if ( !TestNGClassFinder.isTestNGClass( testSet.getTestClass(), annotationFinder ) )
> {
> xmlTest.setJUnit( true );
> }
--
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