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] - junit per-test-method fork mode
Date Tue, 11 Jul 2006 20:52:15 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


jkf@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Additional Comments From jkf@apache.org  2006-07-11 20:52 -------
It also seems to me that this is more in the junit ballpark than in ant's
ballpark, junit isn't offering test method isolation functionality.

1) In case a high level of isolation is needed, tests should be declared in
separate classes.

2) Although testcases should not depend on each other, test runs should be
repeatable, this implies the order should be fixed.

3) When debugging strange crashes within one testcase, I'd recommend to use a gui.

So unless you get one of your students to produce something that does this, 
and isn't too ugly to be included,
and works with junit 3.8 and higher,
and works with java 1.2 and higher,
and has testcases,
chances are very next to zero that something will happen.

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