... and I have already answered to you ... There is nothing costly if you refactor your unit tests around their fixtures (which is the way it should be).
-Vincent > -----Original Message----- > From: Anil Agrawal [mailto:[EMAIL PROTECTED] > Sent: 03 July 2003 07:08 > To: Cactus Users List > Subject: RE: Same session tests > > Hi Scott, > > We are sailing in the same boat. > > I also requested vincent many times that we must have a facility by > which > > once a attribute is set in session It should not be remoce from > session > > unless explicitly removed from session. > > Session Management is very costly per method. > > With regards > anil > > > > -----Original Message----- > From: Parmley, Scott C. [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 03, 2003 3:39 AM > To: [EMAIL PROTECTED] > Subject: Same session tests > > > Hello all, > > I have an issue I need some advice on. I have finally been able to put > together a cactus test that examines an HttpSession. I am using > RequestDispatcher to forward a request to an XSP page. The page does > some work and populates a session variable with an object. Here's my > quandary: > > I must perform a series of tests in order. The first part to be done is > logging in. This, as I mentioned before, populates a session variable > with an object. The next test, which is not logging in, is dependent on > the use of the same session as was used in the first test. > > What I have noticed is that if I write a test class that contains more > than one test (i.e. testXXX() testYYY() ), they utilize different > sessions for each test. Is there a way to write a test class such that > each subsequent test uses the same HttpSession? > > > Thanks in advance, > -Scott > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
