[ 
https://jira.codehaus.org/browse/SUREFIRE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353229#comment-353229
 ] 

Michal Bocek commented on SUREFIRE-1096:
----------------------------------------

Sounds good. At the moment we decided to use different strategy of test 
execution but it will be nice to know that more "suites.xml" files will be 
possible to execute in forked jvms. 

Thank you.

> ClassCastException: Fork test for TestNG with xmlsuite
> ------------------------------------------------------
>
>                 Key: SUREFIRE-1096
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1096
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: TestNG support
>    Affects Versions: 2.14, 2.15, 2.16, 2.17
>            Reporter: Michal Bocek
>            Assignee: Andreas Gudian
>             Fix For: 2.18
>
>
> When i setup surefire for forking tests via:
> <forkCount>3</forkCount>
> <reuseForks>true</reuseForks>
> <parallel>false</parallel>
> And i'm using TestNG provider with xml suite definition:
> <suiteXmlFiles>
> <suiteXmlFile>suite.xml</suiteXmlFile>
> </suiteXmlFiles>
> I'm getting exception:
> Caused by: java.lang.ClassCastException: java.io.File cannot be cast to 
> java.lang.Class
>       at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:201)
>       at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:160)
>       at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:806)
>       at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:701)
>       at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:629)
>       at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to