[
https://jira.codehaus.org/browse/SUREFIRE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320399#comment-320399
]
Steve Loughran commented on SUREFIRE-966:
-----------------------------------------
# -yes, testing test runners, especially things like timeouts are brutal:
debugging problems even harder.
# regarding making the timeout a default in JUnit, it's really a hint for the
test runner: the surefire runner interprets "0" as "forever", so there's
already some implicit defaulting going on there.
# the only question then is which JUnit test runner -I'd assumed there was a
custom Surefire one. If not, then yes, this is very much a JUnit issue -though
if and when its runner got a default timeout, we'd then need a way of passing
it down.
# @Andreas -thanks for the introduction to {{@RunWith}}. If we can do our own
testrunner extension of the standard one, we can not only set our defaults, we
can bundle it internally and so roll it out on a schedule that suits us.
Thanks for the feedback, closing as WONTFIX
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
