I guess what I like about cactus is that I don't have to start Turbine etc... It is all running for me.. And does the whole container testing... Then, using Canoo, I can test easily from a web browser perspective..
The key thing though is that you TEST your code, regardless of what strategy you use... ERic -----Original Message----- From: Chris K Chew [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2003 1:13 PM To: Turbine Users List Subject: RE: Testing -- Cactus v EasyMock > From: brian janaszek > > What framework have people had the best luck with? Around here we use Junit and HttpUnit with much success. Using a Junit base test case that starts Turbine, we can easily test OM classes, services, and screen classes. Templates and the User-experience as a whole is tested with HttpUnit through http and the actual container. Some people have been using Canoo Webtest in lieu of HttpUnit, which seems like a pretty cool package. We have looked into cactus a few times, but fail see where it will pay off -- we can already test Turbine facilities with straight junit, and httpunit allows us to actually test container compatibility. Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
