[
https://jira.codehaus.org/browse/SUREFIRE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283206#comment-283206
]
nkeywal edited comment on SUREFIRE-786 at 11/10/11 8:28 AM:
------------------------------------------------------------
The patch fixes the issue for the classes. Only the needed class tests will be
executed.
This do not cover the case when only a subset of test methods should be
executed within a class test: all methods will be executed. It seems that the
filters are lost during the fork when forkMode=always (while it works with
forkMode=once). For us, as we use tags on classes and all classes are tagged,
it's enough anyway.
was (Author: nkeywal):
The patch fixes the issue for the classes. Only the needed class tests will
be executed.
This do not cover the case when only a subset of tests should be executed. It
seems that the filters are lost during the fork when forkMode=always (while it
works for forkMode=once). For us, as we use tags on classes and all classes are
tagged, it's enough anyway.
> JUnit @Category are not taken into account if forkMode=always
> -------------------------------------------------------------
>
> Key: SUREFIRE-786
> URL: https://jira.codehaus.org/browse/SUREFIRE-786
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.11
> Reporter: nkeywal
> Attachments: JUnit48TestCategoriesForkIT.java, surefire786_trunk.patch
>
>
> Selection by groups works if forkMode=once or none. Whith forkMode=always, it
> seems that all tests are executed.
> See attachment for a test case.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
