ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39995] New: - junit per-test-method fork mode
Date Sat, 08 Jul 2006 22:05:50 GMT
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=39995>.
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=39995

           Summary: junit per-test-method fork mode
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: bmaurer@andrew.cmu.edu


Currently, the junit mode's most granular fork level is per testcase (eg, per
class). Having a per test method fork level would help in cases where high
levels of isolation are needed. A few use cases:

1. I'm using ant to execute junit tests on students' code to determine part of
their grade. Often, a student will fail one test case due to a timeout. However,
this failure causes ant to not get a score for any other method in that class.
While junit4 has a "timeout" field on the test attribute, java lacks a safe way
to forcefully abort a thread. As a result, a junit4 style timeout often causes
other test cases to timeout (because the rogue thread is still running). Per
method isolation would greatly ease this problem.

2. Sometimes, one wants to know if test cases depend on being executed in a
specific order. Per method isolation would help.

3. When debugging "strange" crashes, it often helps to isolate test runs. For
example, if there were an out of memory exception in test Y, it's quite possible
that test X actually has a leak, but didn't allocate quite enough memory to
cause the exception. By running in isolation, it'd be easier to tack this down.

-- 
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


Mime
View raw message