[
https://jira.codehaus.org/browse/SUREFIRE-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338372#comment-338372
]
Leonardo Leite commented on SUREFIRE-1049:
------------------------------------------
Ouch!
I just built a very simple project and it happened what you said, the desired
behavior!
I also verified the desired behavior in another project of mine!
However, in a specific project I still got the reported undesired behavior.
The project started with a giant pom built by someone else... I suspect
something in this giant pom
is responsible by the problem.
Here is the pom:
https://github.com/choreos/enactment_engine/blob/master/pom.xml.
Here is the mvn test output:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2,
useUnlimitedThreads=false
Running org.ow2.choreos.invoker.InvokerHistoryTest
Here, the {{Running org.ow2...}} is printed just after the test is completed.
I think the {{Concurrency config...}} line is a kind of suspicious too.
The test framework used in all the cases was JUnit 4.
Thanks,
Leonardo Leite
> Printing "running test" after test is completed
> -----------------------------------------------
>
> Key: SUREFIRE-1049
> URL: https://jira.codehaus.org/browse/SUREFIRE-1049
> Project: Maven Surefire
> Issue Type: Bug
> Environment: At least Linux, but I believe all environments are
> affected.
> Reporter: Leonardo Leite
> Priority: Trivial
>
> Problem: the message "running <test name>" is printed just after the test is
> completed, being printed together the message "Tests run: X, Failures: Y ...".
> Consequence: when a test gets frozen, I do not know which test is frozen!
> Desired behavior: print "running <test name>" when the test execution starts,
> and print "Tests run: X, Failures: Y ..." when the test execution finishes.
--
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
