[
https://jira.codehaus.org/browse/SUREFIRE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320333#comment-320333
]
Kristian Rosenvold commented on SUREFIRE-966:
---------------------------------------------
Surefire has the timeout on the fork, which could be used in conjunction with
forkMode=always to get individually controlled results. Technically the report
for a timed out test /should/ be correct, so if it is not, that is a bug.
(The code/logic around the timeout logic is a real PITA to test, so any bugs in
this area do not surprise me).
I had some indications in private email that the problem MIGHT be that surefire
does not correctly report status for the testcase that is being run at the
instant it times out. This sounds like a bug. We should be reporting status for
the current testcase when we terminate due to timeouts. Please consider
adapting surefire-integratuion-tests/src/test/resources/fork-timeout/ and the
corresponding IT to illustrate this problem.
> Add ability to set a default timeout on all JUnit4 tests that don't set one
> explicitly
> --------------------------------------------------------------------------------------
>
> Key: SUREFIRE-966
> URL: https://jira.codehaus.org/browse/SUREFIRE-966
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.x support
> Affects Versions: 2.13
> Reporter: Steve Loughran
> Priority: Minor
>
> add ability to set a default timeout on for JUnit4 tests that don't set one
> in their attributes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
