Benjamin's links are the right place to start, though I might add that the
head of that thread is a really long e-mail from me that doesn't directly
address your question. The rest of the thread is about your question.
Executive summary: TestNG support was broken in Surefire 2.3.x; it only
worked in certain simple cases. In Surefire 2.4 we give more control over
to TestNG, fixing the functional errors, but reducing our ability to log,
because TestNG doesn't call us back at the right times. There is no
option to switch back to the old mostly-broken behavior.
If this feature matters (in the linked thread I argue that it doesn't
matter very much) then users should pester the TestNG team to provide
support for it, by creating an "onClassStart"/"onClassFinish" event that
Surefire can use.
-Dan
Benjamin Bentmann wrote:
Surefire-2.3.1 used to output which test was running and it would create
an output file for each test.
I am using testng. Can anyone tell me why this changed and if there is
any way to configure it to behave in the same manner as previous
releases?
Nice to see I am not the only one who is missing that after trying Surefire
2.4 out... You might want to look at
- http://jira.codehaus.org/browse/SUREFIRE-433
-
http://www.nabble.com/Test-Suites%2C-Ant%2C-Surefire%2C-and-JunitReport-to15076378.html#a15076378
As a workaround, I tried to set forkMode=always to get test-per-class
behavior back but ended again in some discussion:
- http://jira.codehaus.org/browse/SUREFIRE-446
-
http://www.nabble.com/testng%2C-surefire%2C-and-forkMode%3Dalways-to15323782.html
Regards,
Benjamin Bentmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
