At 08:46 AM 7/6/2001 +0100, Vincent Massol wrote: >----- Original Message ----- >From: "Gogineni, Pratima" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Thursday, July 05, 2001 5:31 PM >Subject: RE: [cactus] Supporting security in Cactus and Cacus Design (WAS >Re: Cactus with container security) > > I guess essentially what I am saying is it would be good if cactus > supported > > both in container and mock object testing and leave it upto the programmer > > to figure out which is appropriate in a particular case. > > > >I agree with you. However, it is not that easy to integrate both and I am >still struggling to find a way of doing so ... What I mean by integrate is >simply to have a common way of writing a test case which could then be run >either in-container or mock style. If you have ideas please do submit them >on the list. Well, ServletUnit supports mock-object testing, and we have already spoken of a possible synergy between HttpUnit and Cactus (beyond the work now ready to be committed to cvs and waiting for sourceforge.net to get cvs working again), so... If it were possible to use HttpUnit code to actually define the requests and handle the results.... and if we can somehow homogenize the way ServletUnit and Cactus provide access to an active servlet... it may be possible to allow users to switch back and forth between Cactus (in-container tests) and ServletUnit (mock-object tests) relatively easily.
