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 [EMAIL PROTECTED] 2001-11-15 14:30 ------- I'm sorry if my initial description of the problem wasn't too clear, I was in a hurry when I wrote it. I don't think that keeping tests in a separate package is wrong, especially when this package is a subpackage to the package being tested as in your example. But in some cases, test cases that need access to package methods might be needed. I have even used test cases implemented in static inner classes to test really internal mechanisms of some classes. The main issue of my enhancement request is a way to define the connection between classes or packages and their test cases that works in any of the situations above. Keeping the javadoc tag in an ant or junit namespace sounds like a good idea. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
