Hmmm, the bug says it is fixed in 2.4.1 and it still produces a single suite file and single suite output to the console. I agree with you Benjamin, I don't think Dan understood the problem and thus didn't actually fix it. Instead, the fix was for the reporting.
-----Original Message----- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 3:15 PM To: Maven Developers List; Maven Users List Subject: Re: changes to surefire output with testng Hi, > 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-to1532 3782.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]
