DO NOT REPLY [Bug 35877] New: - JUnit timeout description is not quite accurate

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35877>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35877

           Summary: JUnit timeout description is not quite accurate
           Product: Ant
           Version: 1.6.5
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: minor
          Priority: P4
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: Mark.Doliner@sas.com


The documentation for Junit's "timeout" property states, "Cancel the individual
tests if they don't finish in the given time (measured in milliseconds). Ignored
if fork is disabled."  However, this is no longer always accurate.

If you're using a nested <batchtest> and forkmode="once" then the timeout
applies to the time taken by all tests combined and NOT each test individually.

An easy fix would be to change the documentation to read: "Cancel the forked JVM
if the test(s) don't finish in the given time (measured in milliseconds). 
Ignored if fork is disabled."

A possibly better fix would be to change the watchdog implementation so that it
really does affect each test (instead of affecting the entire batchtest).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org