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 2956] - patch to junit and touch task: junit task now wont fail on non-junit test, touch now provides the same timestamp for all files when operating on a fileset
Date Wed, 06 Feb 2002 19:56:32 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2956>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2956

patch to junit and touch task: junit task now wont fail on non-junit test, touch now provides
the same timestamp for all files when operating on a fileset





------- Additional Comments From sbailliez@apache.org  2002-02-06 19:56 -------
The JUnit logic for extracting a test is as follows (latest runner from Erich 
Gamma in Eclipse):

1) create instance of class using default ctor. (remember a TestCase has 
normally a String ctor)
2) if instanceof TestSuite return;
3) invoke static suite() method returning a Test and return if no error
4) wrap the class around a TestSuite and return if no error
5) return null

That means that you can have any class successfully considered a test as long 
as it it has a static suite() method returning a class. No need for it to be a 
Test itself (which can be a decorator anyway)

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


Mime
View raw message