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 26165] - Type checking in JUnit batchtest
Date Thu, 03 Nov 2005 14:23:04 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=26165>.
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=26165





------- Additional Comments From badorek_jeffrey_w@cat.com  2005-11-03 15:23 -------
Created an attachment (id=16868)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=16868&action=view)
Type checking JUnitTask

This little extension extends the current JUnitTask and uses bcel to do the
type checking you are talking about. It checks that a class extends
junit.framework.TestCase or has a static method called "suite()". In addition,
it also checks that the class is public and not abstract.

I've also added a couple of new properties to include/exclude types to check.
For instance, by default I have includedTypes="junit.framework.TestCase" and
excludedTypes="net.sourceforge.jwebunit.WebTestCase". This way, any class that
extends WebTestCase, won't be run.

All in all, I think that at the very least, the type checking for
"junit.framework.TestCase" could be added to the original JUnitTask.

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