[
https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284307#comment-284307
]
Kristian Rosenvold commented on SUREFIRE-798:
---------------------------------------------
I assume you're thinking about /when running in serial/ ? For all kinds of
parallel, the current behaviour will not change, since it keeps output linear.
> JUnit47 provider could print immediatly the test class name, as JUnit4,
> instead of waiting for the test to finish.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-798
> URL: https://jira.codehaus.org/browse/SUREFIRE-798
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.7+ (parallel) support
> Affects Versions: 2.10
> Environment: all
> Reporter: nkeywal
> Priority: Minor
>
> With a test that takes some time, for example
> {noformat}
> public class Test0 {
> @Test
> public void testT0() throws Exception {
> Thread.sleep(6000);
> }
> }
> {noformat}
> With JUnit4, we have first
> {noformat}Running Test0{noformat}
> Then, 6 seconds later
> {noformat}Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 6.002 sec{noformat}
> With JUnit47, we wait for 6 seconds, then the two lines appear simultaneously.
> The former behavior is better, because it allows to kill the test if we know
> that this test should not take so long. It also gives the feeling that you
> know what's going on :-).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
