Hi JB, > -----Original Message----- > From: J. B. Rainsberger [mailto:[EMAIL PROTECTED] > Sent: 24 November 2003 00:00 > To: Cactus Users List > Subject: Re: Asking Questions > > Owen Chau wrote: > > > Cactus supports "integration unit testing". Can you explain > > the nature of this "integration" you refer to. > > Integration Tests exercise multiple objects together. Object Tests > exercise a single object in isolation, usually by faking its > collaborators. > > > 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? > > In theory, if you have 100% Object Test coverage /and/ perfect > interface/implementation separation, then Integration Tests are > unnecessary. Since no-one has 100% Object Test coverage /and/ perfect > interface/implementation separation, Integration Tests are necessary to > plug the holes.
I don't quite agree! :-) You're only talking about integration between components themselves. Where is the integration with the container/database/etc tested? All the meta-data files (config files, deployment descriptors, etc) do not get tested with object test coverage, right? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
