juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Cutright <acutri...@borland.com>
Subject [juddi-Developers] using junit
Date Thu, 29 May 2003 16:09:06 GMT
hi steve, et.al.,

i've read the junit 'cookbook'. i want to understand your goals for the 
test suite. do you want to use junit to provide automated testing, and 
standard error reporting? and to provide a common framework / style to 
make the suite easily extensible/ maintained?

i think my few tests can extend junit's TestCase base class. they 
already offer a run() method, in the junit style. junit has some strong 
points. i like the setup()/ teardown() idea. i don't want test cases 
creating artifacts that will affect other classes. being a standards guy 
(CORBA/ J2EE), i like a well documented standard. and the fact that it's 
already -documented- is nice too. my concern is style i suppose: the 
juddi test cases are sufficiently complex that imposing the formal 
structure of setup()/ run()/ shutdown() isn't going to scale, imo.

if we make each test class extend TestCase and implement the run(), 
we'll still be able to use the standard junit error reporting, and the 
junit test harnesses. i'll have some working examples tomorrow afternoon.

thoughts?

cheers,
andy



Mime
View raw message