[
https://issues.apache.org/jira/browse/SUREFIRE-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023723#comment-17023723
]
Kishore Kumar commented on SUREFIRE-1745:
-----------------------------------------
[~tibordigana]
_forkedProcessTimeoutInSeconds_ works fine only if the _parallel_ is not
enabled. Also, it kills the entire fork, which is not the expected behavior for
our use-case.
I'll work on the feature of a global timeout as per your guidelines.
Apart from this, I'm still not sure about what is the best approach to run the
test in parallel (with Junit 4) i.e using fork or parallel (classes/ methods)
or both, also what should be forkNumber/Threadcount for the best performance
(total time). It would be really appreciable if you provide some reference for
same.
> 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)
