[
http://jira.codehaus.org/browse/SUREFIRE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135649#action_135649
]
Joel Wiegman commented on SUREFIRE-446:
---------------------------------------
I'm suffering from this as well. The 2.4-collab-SNAPSHOT has plenty of unfixed
bugs and I unfortunately cannot use this version.
As for forkMode=always, this is a relatively common practice in unit tests.
Consider the following scenarios:
1. I have a crucial static variable and would like it reset to a known state
for each test / test class
2. I bootstrap my unit tests with some data by using an in-memory database
that's created on the fly and would like it to be reset to a known state for
each test/test class as well
In either of these scenarios, the only way to return to a known state in a unit
test is to ensure you're starting with a fresh JVM.
I get that TestNG offers some testing functionality that is "outside" the unit
testing paradigm (@BeforeSuite and @AfterSuite), but I agree with Benjamin...
let's let the developer use whatever configuration he/she wants and let them
make their own mistakes.
> Surefire fails to capture TestNG results when forkMode=always
> -------------------------------------------------------------
>
> Key: SUREFIRE-446
> URL: http://jira.codehaus.org/browse/SUREFIRE-446
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4
> Environment: Maven 2.0.8, JDK 1.5.0_12, WinXP
> Reporter: Benjamin Bentmann
> Fix For: 2.x
>
> Attachments: testng-fork-mode-it.patch
>
>
> The interplay between {{surefire.Surefire}} and
> {{testng.TestNGDirectoryTestSuite}} does not properly notify the
> ReportManager such that it reports 0 executed tests after the end of the day.
> IT to reproduce attached.
> Also confirmed against 2.5-SNAPSHOT.
--
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
