[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-04-04 Thread Andreas Gudian (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Gudian updated SUREFIRE-968:


Description: 
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.

  was:
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.

 Issue Type: Improvement  (was: Bug)

> 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: Improvement
>  Components: Maven Surefire Plugin
>Affects Versions: 2.14
> Environment: Ubuntu, JDK 7
>Reporter: Jesse Glick
>Assignee: Andreas Gudian
>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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-04-04 Thread Andreas Gudian (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Gudian closed SUREFIRE-968.
---

   Resolution: Fixed
Fix Version/s: (was: 2.14.1)
   2.15

> 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
>Assignee: Andreas Gudian
>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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-04-04 Thread Andreas Gudian (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Gudian reassigned SUREFIRE-968:
---

Assignee: Andreas Gudian

> 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
>Assignee: Andreas Gudian
>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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-04-02 Thread Nicolas Liochon (JIRA) 

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

Nicolas Liochon commented on SUREFIRE-968:
--

bq. How about this?
+1 from me :-).

> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-04-02 Thread Andreas Gudian (JIRA) 

[ 
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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-16 Thread Andreas Gudian (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Gudian updated SUREFIRE-968:


Fix Version/s: 2.15

> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-16 Thread nkeywal (JIRA) 

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

nkeywal commented on SUREFIRE-968:
--

The single line one has the advantage of beeing easier to grep & sort. And it 
uses less lines on the screen :-).

Even with the previous versions of surefire it was possible have mixed lines 
when using any kind of parallel test. Just that now it happens all the time.
This does not happen when everything is on one line.


> 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
>
> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-14 Thread Kristian Rosenvold (JIRA) 

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

Kristian Rosenvold commented on SUREFIRE-968:
-

I did not check this; but for concurrent forks I think we probably loose the 
synchronization, since that was created with single forks in mind.

> 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
>
> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-13 Thread Andreas Gudian (JIRA) 

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

Andreas Gudian commented on SUREFIRE-968:
-

> Netbeans does for example to populate the JUnit window output.

Meeh, thought so. I guess changing the output to something like the following 
would _break_ quite a number of third party and user-created tooling:

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

But how about this one?

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

I would guess that this would not break that many output parsers out there.

What do you think?

@Kristian: all the "live" output routing is already synced perfectly, you're 
right. This is just about that output created in {{ConsoleReporter}} on 
{{testSetStarting}} and {{testSetCompleted}}.

> 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
>
> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-13 Thread Andreas Gudian (JIRA) 

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

Andreas Gudian edited comment on SUREFIRE-968 at 3/13/13 2:56 PM:
--

> Netbeans does for example to populate the JUnit window output.

Meeh, thought so. I guess changing the output to something like the following 
would _break_ quite a number of third party and user-created tooling (plus, 
it's harder to read):

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

But how about this one?

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

I would guess that this would not break that many output parsers out there.

What do you think?

@Kristian: all the "live" output routing is already synced perfectly, you're 
right. This is just about that output created in {{ConsoleReporter}} on 
{{testSetStarting}} and {{testSetCompleted}}.

  was (Author: agudian):
> Netbeans does for example to populate the JUnit window output.

Meeh, thought so. I guess changing the output to something like the following 
would _break_ quite a number of third party and user-created tooling:

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

But how about this one?

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

I would guess that this would not break that many output parsers out there.

What do you think?

@Kristian: all the "live" output routing is already synced perfectly, you're 
right. This is just about that output created in {{ConsoleReporter}} on 
{{testSetStarting}} and {{testSetCompleted}}.
  
> 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
>
> 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:

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-13 Thread Kristian Rosenvold (JIRA) 

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

Kristian Rosenvold commented on SUREFIRE-968:
-

This should actually be fairly easy to fix, since its all about synchronizing 
the playback of the captured output data. Im a bit surprised this actually isnt 
the case already, but I believe you guys ;)

> 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
>
> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-13 Thread Milos Kleint (JIRA) 

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

Milos Kleint commented on SUREFIRE-968:
---

> @Kristian: do you know of any major third party tools that parse that output 
> (on stdout or in the txt file)?

Netbeans does for example to populate the JUnit window output.

> 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
>
> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-13 Thread Andreas Gudian (JIRA) 

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

Andreas Gudian commented on SUREFIRE-968:
-

You're right, that's a bit annoying. 

@Kristian: do you know of any major third party tools that parse that output 
(on stdout or in the txt file)?

> 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
>
> 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

[jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency

2013-03-08 Thread Jesse Glick (JIRA) 
Jesse Glick created SUREFIRE-968:


 Summary: 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


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