Hi - I have used Cactus for testing. Cactus does a good job of testing the objects used by Tapestry (my case, EJBs). To test Tapestry pages and components, you may want to look at the HTTPUnit/HTTPClient. HTTPUnit works with Cactus and is supposed to help test web pages. I have not tried using it yet.
Dorothy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 8:22 AM To: Dennis Yarborough Cc: [EMAIL PROTECTED] Subject: [Tapestry-developer] Re: unit testing tapestry applications I'm very pleased that you've been having so much success with Tapestry. I have been thinking along similar lines; I would really like to create more unit tests for Tapestry; only a few things around the edges are currently unit tested. There seem to be two approaches to this. MockObjects: Implementations of all the servlet stuff as some kind of controllable objects. Kind of like simulating the web application layer in a controllable, predictable way. Cactus: seems to involve running the application in one JVM and running the tests in another. I haven't had much experience with either of these. If I had more time, I would probably go with the MockObjects approach for testing the framework itself. For your purposes, so, I suspect Cactus might be a better fit. -- [EMAIL PROTECTED] http://tapestry.sf.net > Our group has successfully deployed several > > applications using the tapestry framework. We > > have been focusing over the last several months > > on getting the applications designed, built and > > deployed. We are now at a point that we need to > > bring several teams together and devise a common > > approach towards unit testing our applications. > > Our applications are build with several > > architectural layers that we would like to devise > > a mechanism for automating the unit test process > > (ie. nightly build). The layers we are interested > > in unit testing at this point are web (tapestry), > > service, and persistence layers. My question is > > do you know anybody with a good approach to unit > > testing tapestry applications, specifically the > > web layer (jwc, html, java). Even the service > > layer which interacts with the web layer present > > several problems with automated unit tests when > > interfacing the the tapestry framework. Our goal > > (if possible) is to provide unit tests that are > > pass/fail and not rely on manual inspection of > > output to determine of the code works or not. > > We are extremely pleased with the framework, it's > > just that we would like some insight on your > > thoughts on best approaches towards unit testing. > > > > Dennis Yarborough > > [EMAIL PROTECTED] > > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that�s a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
