You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/12/12 13:32:46 UTC

[jira] [Comment Edited] (SUREFIRE-1207) A new JVM is forked even for tests not matching the "groups" tag when "reuseForks" is false

    [ https://issues.apache.org/jira/browse/SUREFIRE-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054271#comment-15054271 ] 

Tibor Digana edited comment on SUREFIRE-1207 at 12/12/15 12:31 PM:
-------------------------------------------------------------------

[~MComerford]
Would you open a pull-request for this issue in GitHub?
You should implement Filter of test classes which use annotations @Test(groups) in TestNG classes or @Category in JUnit. If you need any help feel free to ask.


was (Author: tibor17):
[~MComerford]
Would you open a pull-request for this issue in GutHub?
You should implement Filter of test classes which use annotations @Test(groups) in TestNG classes or @Category in JUnit. If you need any help feel free to ask.

> A new JVM is forked even for tests not matching the "groups" tag when "reuseForks" is false
> -------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1207
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1207
>             Project: Maven Surefire
>          Issue Type: Improvement
>    Affects Versions: 2.18.1
>            Reporter: Michael Comerford
>             Fix For: Backlog
>
>
> When the "groups" tag is used with "resuseForks" as false, a new fork is created for every test, not just the one in the group tag. The tests which don't match the group aren't ran, but a fork is still created and destroyed for every test, which is very inefficient.
> Example:
> {code:xml}
> <plugin>
>     <artifactId>maven-surefire-plugin</artifactId>
>     <configuration>
>         <skip>true</skip>
>     </configuration>
>     <executions>
>         <execution>
>             <id>default-tests</id>
>             <phase>test</phase>
>             <goals>
>                 <goal>test</goal>
>             </goals>
>             <configuration>
>                 <skip>false</skip>
>                 <excludedGroups>IsolatedTests</excludedGroups>
>             </configuration>
>         </execution>
>         <execution>
>             <id>isolatedTests</id>
>             <phase>test</phase>
>             <goals>
>                 <goal>test</goal>
>             </goals>
>             <configuration>
>                 <skip>false</skip>
>                 <groups>IsolatedTests</groups>
>                 <forkCount>1</forkCount>
>                 <reuseForks>false</reuseForks>
>             </configuration>
>         </execution>
>     </executions>
> </plugin>
> {code}
> The forking can be seen when running maven in debug mode: {{mvn test -X}} and searching for the text "Forking command line"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)