Correct, the mockobjects.com project has the servlet mock classes. I've been using EasyMock with some success ( easymock.org ). I have a trivial example here http://jakarta.apache.org/turbine/tdk/application-testing.html which uses easymock to mock rundata and context into a t2.2 action. Along those lines, you could always use the rttest harness and cactus to test in the container, but this is a slower option. I'm coming into this thread late, but am willing to help out with the testing where I can.
jb ================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 21, 2002 12:22 PM > To: Turbine Developers List > Subject: RE: [PATCH] T3 - DynamicURI > > > On Thu, 2002-03-21 at 12:32, Stephane Bailliez wrote: > > > -----Original Message----- > > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]] > > > > > Add tests if you can stephane, that would be very much > appreciate I > > > think it is extremely important to test the changes we're > making in t3 > > > to make sure the groundwork is solid. > > > > Actually it is not that easy. We should create a couple of > mock objects and > > make them available as part of main turbine code (or > extension) for people > > that need to test their own derived classes. there is a > need for an mock > > httpservletrequest, response, servletcontext, > servletconfig, etc... as well > > as a BaseTurbineTestCase > > > > does someone has any experience with mock objects ? > (mockmacker and such ?) > > I think that Jeff does, but I will start learning so I can > help practice > what I preach. I am going to be adamant about including testing code > with changes in t3. My changes in the branch are fully > functional but I > have no tests so I haven't merged it. I don't believe there is much > value in making changes now without the tests. We have > historically had > a great deal of trouble figuring out exactly how things work > when things > go wrong: it's usually guess work trying to figure out exactly how > something is working and that has to stop. I know people are > now trying > to use t3 in production but reliability and deterministic behaviour is > the first priority IMO. > > That being said I will read about mock objects and help > create the base > mock objects we need for testing. I think Jeff has done a lot > of work in > this area and I imagine there has to be mock objects already made for > standard web objects. > > > Stephane > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
