FYI: I've moved this reply to the turbine-user list. We've started some documentation for testing of applications developed with the Turbine family of frameworks. It is far from complete and is starting out as a place to list some best practices for testing with regards to Turbine applications.
http://jakarta.apache.org/turbine/tdk/application-testing.html The Turbine 3 CVS repository has run-time tests integrated into the build using cactus. Now that the t3 integration tests are working, I'm planning to write up an addition to the above site outlining how to integrate cactus with a Turbine application for testing. Any comments or additions are welcome! ----------------------------------------------------------------- Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com ----------------------------------------------------------------- > -----Original Message----- > From: Colm McCartan [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 24, 2002 9:59 AM > To: Turbine Developers List > Subject: Cactus (Was:Re: RunData & Security Changes) > > > > > I was chatting with Jeff yesterday and I think the next > thing to tackle on a > > first pass is development methodology. The CVS model of the > TDK works pretty > > much like Scarab but I would like to clean up the torque > stuff, add some > > cactus testing for the client side and introduce some > continuous integration > > techniques using Maven. > > > As a matter of interest, are there any examples of integrated Cactus > tests in CVS at the moment? I'm interested in building some > test suites > for tdk (2.1) apps. > > cheers, > colm > ................................................................ > colm mccartan > panasonic owl uk > [EMAIL PROTECTED] > (44) 131 561 1035 > > > -- > 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]>
