maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-968) Test summary line does not indicate what was being run when using concurrency
Date Thu, 04 Apr 2013 21:20:53 GMT

     [ 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

Mime
View raw message