[
https://jira.codehaus.org/browse/SUREFIRE-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1149.
----------------------------------
Resolution: Duplicate
(fork) Duplicate issue. See SUREFIRE-1138 - workaround is available.
(parallel) Not A Bug
I could not find any issue with parameter "parallel".
(the time reported wrong which is another known issue)
Here each test method sleeps for 10 sec. IT test set completes within 10
seconds. Takes IT from a1 artifact.
{code}
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>g</groupId>
<artifactId>a1</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>g</groupId>
<artifactId>a2</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-failsafe-plugin</artifactId>
<version>2.18.1</version>
<executions>
<execution>
<id>it</id>
<goals>
<goal>integration-test</goal>
<goal>verify</goal>
</goals>
</execution>
</executions>
<configuration>
<parallel>all</parallel>
<useUnlimitedThreads>true</useUnlimitedThreads>
<dependenciesToScan>
<dependency>g:a1</dependency>
</dependenciesToScan>
</configuration>
</plugin>
</plugins>
</build>
{code}
> Tests from dependency jar ignore parallel execution
> ---------------------------------------------------
>
> Key: SUREFIRE-1149
> URL: https://jira.codehaus.org/browse/SUREFIRE-1149
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin, process forking
> Affects Versions: 2.18.1
> Reporter: Christopher Smith
> Attachments: pom.xml
>
>
> I have a Selenium test suite that is contained in a module of my main
> application but that needs to be run against an instance deployed to a
> staging environment. I package the tests into a jar and have a separate POM
> that declares {{dependenciesToScan}} and is executed in a later CI step. The
> tests execute, but the runner completely ignores any parallel configuration:
> neither {{parallel}} nor {{forkCount}} has any effect. The debug log shows
> that the plugin is switching to parallel mode, but then it runs them serially
> in a single Java process. As these are browser-driving tests, serial
> execution drastically increases running time.
> Running the tests directly from the main project tree using {{mvn
> failsafe:integration-test -DforkCount=3}} forks multiple JVMs and executes
> the tests in parallel.
> The attached POM is the one used to execute the tests after deployment, and
> which ignores parallel execution for test from the jar.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
