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