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 4886] - JUnit task enhancement
Date Thu, 15 Nov 2001 23:07:25 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=4886>.
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=4886

JUnit task enhancement





------- Additional Comments From sbailliez@apache.org  2001-11-15 15:07 -------
I'm puzzled by your proposal.

This problem is easily solved by adopting naming guidelines for testcases.
In my company all JUnit testcases are prefixed by TestCase, in Ant all JUnit 
testcases are postfixed by Test.
The classic trick is also to use a different directory for TestCase that match 
exactly the structure of the source code, this way you don't have to import the 
classes you test, and you have package access.

This kind of guidelines makes it easy to set a consistent filter on sources and 
has the benefit as well to distinguish easily testcases in an IDE source 
browser.

If such thing has to be done it would probably be easier and more reliable to 
use the bytecode information than a tag in the source code. If it extends 
TestCase and is not abstract obviouslly it's a candidate. :)

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