[ https://issues.apache.org/jira/browse/SUREFIRE-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022866#comment-17022866 ]
Tibor Digana commented on SUREFIRE-1745: ---------------------------------------- [~kishoretak] I think you used another config parameter. There are two similar names: _forkedProcessTimeoutInSeconds _ _forkedProcessExitTimeoutInSeconds_ You mentioned both in your comment but i was talking about *forkedProcessTimeoutInSeconds*. The second one _forkedProcessExitTimeoutInSeconds _has different behavior - see doc. Maybe you can implement this feature o a global timeout. You have to make the reseach. IMO the _Computer_ or _Request_ should be implemented. Those are interfaces from the JUnit4. > Global Junit Test timeout > ------------------------- > > Key: SUREFIRE-1745 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1745 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin > Affects Versions: 3.0.0-M4 > Reporter: Kishore Kumar > Priority: Major > > Hi, > We need unit test level time-out similar to this > [https://github.com/junit-team/junit4/wiki/Timeout-for-tests] in surefire > where we can configure a timeout similar to > _parallelTestsTimeoutForcedInSeconds_. > Also, I've observed that _parallelTestsTimeoutForcedInSeconds_ is not able to > stop the infinite loop kind of test, and for other kinds of test even after > timeout error in the log, the test is marked as successful in the surefire > report. > > Can we have something similar to Junit timeout in surefire where we can > configure global test timeout which will only stop that particular test which > takes more than configured time and mark it as timeout error in the report, > without impacting/stopping any other test's execution? > {code:java} > @Test > public void infiniteLoop(){ > while (true) {} > } > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)