[ 
https://jira.codehaus.org/browse/SUREFIRE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323027#comment-323027
 ] 

Andreas Gudian commented on SUREFIRE-968:
-----------------------------------------

How about this?

{code}
Running org.jvnet.hudson.main.AppTest
Running org.jvnet.hudson.main.UseRecipesWithJenkinsRuleTest
Running org.jvnet.hudson.test.MemoryAssertTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.339 sec, in 
org.jvnet.hudson.main.UseRecipesWithJenkinsRuleTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.539 sec, in 
org.jvnet.hudson.main.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.339 sec, in 
org.jvnet.hudson.test.MemoryAssertTest
{code}

It's in one line, but does not break readability that much - and depending on 
how strict external tools are with their parsing, it might not even break 
_every_ consumer out there.
                
> Test summary line does not indicate what was being run when using concurrency
> -----------------------------------------------------------------------------
>
>                 Key: SUREFIRE-968
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-968
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.14
>         Environment: Ubuntu, JDK 7
>            Reporter: Jesse Glick
>            Priority: Minor
>             Fix For: 2.15
>
>
> When running multiple test suites in parallel, Surefire prints summaries of 
> ongoing test counts, but it is not at all clear which results are being 
> summarized. E.g. with {{forkCount=1C}}:
> {code:none}
> Running CoreJellyTest
> Running org.jvnet.hudson.main.AppTest
> Running org.jvnet.hudson.main.UseRecipesWithJenkinsRuleTest
> Running org.jvnet.hudson.test.MemoryAssertTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.339 sec
> Running org.jvnet.hudson.test.MockFolderTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.719 sec
> Running hudson.bugs.DateConversionTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.867 sec
> Running hudson.bugs.LoginRedirectTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.208 sec
> Running hudson.bugs.JnlpAccessWithSecuredHudsonTest
> Tests run: 538, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.847 sec
> …
> {code}
> It is impossible to tell which results correspond to which test, since there 
> is no way to know which test will finish first. At best you can guess based 
> on the number of test case methods known to be in each class.
> The {{Tests run}} summary line should give the suite name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to