简体   繁体   English

运行JUnit 4测试与FailSafe和SureFire插件并行

[英]Running JUnit 4 Tests Parallel With FailSafe & SureFire plugins

We have a profile created in maven to run our Selenium junit4 type tests and below is the snippet of it without the executions tag. 我们在maven中创建了一个配置文件来运行我们的Selenium junit4类型测试 ,下面是没有执行标记的它的片段。

<profile>
    <id>selenium-tests</id>
    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-failsafe-plugin</artifactId>
                <version>2.11</version>
                <dependencies>
                    <!-- Force using the latest JUnit 47 provider -->
                    <dependency>
                        <groupId>org.apache.maven.surefire</groupId>
                        <artifactId>surefire-junit47</artifactId>
                        <version>2.11</version>
                    </dependency>
                </dependencies>
                <configuration>
                    <parallel>classes</parallel>
                    <threadCount>5</threadCount>
                    <forkMode>pertest</forkMode>
                    <useManifestOnlyJar>false</useManifestOnlyJar>
                    <redirectTestOutputToFile>true</redirectTestOutputToFile>
                    <skip>false</skip>
                    <includes>
                         <include>**/regtests/*.java</include>
                    </includes>
                </configuration>
            </plugin>
        </plugins>
    </build>
</profile>

And my TestClass looks like this. 我的TestClass看起来像这样。

@RunWith(HTMLSourceDumperJUnit4Runner.class) //Our own Runner
public class MyTestClass extends Assert {

     private int x = 1;
     private int y = 1;

     @Test
     public void testAddition() {
         int z = x + y;
         assertEquals(2, z);
     }

}

When I run this testclass through the failsafe plugin 2.11 with parallel configuration it fails with the following error. 当我通过具有并行配置的failsafe插件2.11运行此测试类时,它失败并出现以下错误。

java.lang.Exception: No runnable methods
    at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMethods(BlockJUnit4ClassRunner.java:171)
    at org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:115)
    at org.junit.runners.ParentRunner.validate(ParentRunner.java:269)
    at org.junit.runners.ParentRunner.(ParentRunner.java:66)
    at org.junit.runners.BlockJUnit4ClassRunner.(BlockJUnit4ClassRunner.java:59)
    at org.junit.internal.builders.JUnit4Builder.runnerForClass(JUnit4Builder.java:13)
    at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
    at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
    at org.junit.runner.Computer.getRunner(Computer.java:38)
    at org.apache.maven.surefire.junitcore.ConfigurableParallelComputer.getRunner(ConfigurableParallelComputer.java:142)
    at org.junit.runner.Computer$1.runnerForClass(Computer.java:29)
    at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
    at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:93)
    at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:84)
    at org.junit.runners.Suite.(Suite.java:79)
    at org.junit.runner.Computer.getSuite(Computer.java:26)
    at org.apache.maven.surefire.junitcore.ConfigurableParallelComputer.getSuite(ConfigurableParallelComputer.java:134)
    at org.junit.runner.Request.classes(Request.java:69)
    at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:53)
    at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:140)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
    at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
    at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)

Is there anything I'm missing here. 这里有什么我想念的吗? If I'm lagging any information for this post, please post back. 如果我对这篇文章的任何信息都不满意,请回复。

According the the maven docs on the plugin, specifically the <includes> tag. 根据插件上的maven文档,特别是<includes>标签。 The test class name patterns are: **/IT*.java , **/*IT.java , and **/*ITCase.java . 测试类名称模式为: **/IT*.java**/*IT.java**/*ITCase.java So you'll want to change to name of the class to MyIT or MyITCase or something like that. 因此,您需要将类的名称更改为MyITMyITCase或类似的名称。

http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html#includes http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html#includes

There appears to be a bug in surefire 2.11. surefire 2.11中似乎存在一个错误。 It does not like to function with 它不喜欢功能

<useManifestOnlyJar>false</useManifestOnlyJar>

I filed a bug. 我提交了一个错误。 http://jira.codehaus.org/browse/SUREFIRE-819 http://jira.codehaus.org/browse/SUREFIRE-819

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM