[
http://jira.codehaus.org/browse/SUREFIRE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-568.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.7.2
Assignee: Kristian Rosenvold
Dcoumentation updated in r1058302.
Please also note that it's fairly simple to write a provider that forks per
test method;
fork one of the existing providers and make SurefireProvider.getSuites() return
an iterator that iterates over a list of
fully qualified method names. This will be passed to invoke subsequently.
> Fork mode of "pertest" or "always" does not fork per test or always
> -------------------------------------------------------------------
>
> Key: SUREFIRE-568
> URL: http://jira.codehaus.org/browse/SUREFIRE-568
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 1.3 (2.0-beta-1 plugin), 1.4 (2.0 plugin), 1.5 (2.1
> plugin), 1.5.1 (2.1.1 plugin), 1.5.2 (2.1.2 plugin), 1.5.3 (2.1.3 plugin),
> 2.0 Report Plugin, 2.0 (2.2 plugin), 2.3, 2.3.1, 2.4, 2.4.1, 2.4.2, 2.4.3
> Environment: Windows XP, Java 6 update 14, JUnit 4.6
> Reporter: Laird Nelson
> Assignee: Kristian Rosenvold
> Fix For: 2.7.2
>
>
> Perhaps this is a misunderstanding, in which case I'd ask for a clarification
> in the documentation.
> If I specify a <forkMode> of "always" or "pertest" (which I understand is the
> same thing), Surefire will fork for each test *class*, but *not* for each
> @Test within the test class.
> The documentation led me to believe that surefire would fork once for each
> method annotated as @Test.
> (Background: I'm running OpenEJB and H2, and need to ensure that the
> in-memory H2 database I have set up is zapped in between each test run so
> that, among other things, the automated DDL generation re-runs for each test.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
