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 Fri, 16 Nov 2001 10:16:08 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 erik.agsjo@noptec.com  2001-11-16 02:16 -------
Stephane,

as I wrote in my previous comment, my main concern is not how to organize source
trees, packages or class naming conventions. Clearly there are several methods
of doing this that fit different development situations.

What I would like is some way of seeing, for each class (and maybe each
package), what testcase that is responsible for verifying the functionality. If
we decide to use a javadoc tag for this purpose, then this could also be used to
by ant to find out what testcases to run.

I find it more intuitive to write rules that say "run tests on these classes"
rather than "run these testcases that test something".

If a javadoc tag is used, the "main class" <-> "test case" relationship could be
extracted by a doclet and included in the documentation. We could also specify a
testcase for a whole package by setting javadoc tags in the package
documentation file.

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