Chad, Please have a look as the provided sample application (in sample/ directory where you unzipped the Cactus distribution). You'll see the kind of tests you can perform with Cactus.
WRT database access and any other API, Cactus is completely transparent, meaning there is no interception of any sort (your database will get called). The only interception Cactus does (and which is a transparent interception - if you exclude possible bugs :-)) is with the Servlet and Filter APIs. In other words, with a Cactus test you decide of your entry point in your application to test and it goes all the way at the back (till the database or even calling other remote resources such as some CICS transactions on a mainframe or other partners, etc). If you wish not to go all the way, you can combine a mockobjects strategy with Cactus. Hope it helps, -Vincent > -----Original Message----- > From: chad r [mailto:[EMAIL PROTECTED]] > Sent: 28 March 2002 15:14 > To: [EMAIL PROTECTED] > Subject: is this true? > > > > Hi, > Is Cactus only for testing the cookie and session objects? Can't we test > some code for example some > database code in the servlet? Is it possible with the present cactus > structure to invoke database and get result? Do we need to make any > changes ? > Thanks > chad > > > > > --------------------------------- > Do You Yahoo!? > Yahoo! Movies - coverage of the 74th Academy AwardsR -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
