Hi Owen, Lots of good and difficult questions! :-) It's going to be difficult answering them all here.
For "integration", it means integration with the executing environment (container, database, etc). However, you can combine Cactus with Mock Objects to test integration bit by bit. For example if you don't want to go till the database, you can use mock objects to cut the calling chain. You can also have a look at a presentation I gave for the TSS Symposium about unit testing J2EE applications (It's not completely self supporting but it might give you some answers): http://blogs.codehaus.org/people/vmassol/archives/000080.html Thanks -Vincent > -----Original Message----- > From: Owen Chau [mailto:[EMAIL PROTECTED] > Sent: 21 November 2003 20:51 > To: [EMAIL PROTECTED] > Subject: Asking Questions > > > > Cactus supports "integration unit testing". Can you explain > the nature of this "integration" you refer to. Also, how about the > advantages, > if any, of integration unit testing, as opposed to testing the unit in > isolation. Do we need any additional tool and/techniques to cover the > other > aspects of unit testing? > > _________________________________________________________________ > Linguaphone : Learning English? Get Japanese lessons for FREE > http://go.msnserver.com/HK/30476.asp > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
