Dirk Behrendt wrote: > There are tools for automatic testing the Struts application?
As mentioned the Struts TestCase on SourceForge is a Struts specific tool. It does a good job of directly testing the Struts internals, but to test it all you sometimes need to get Cactus running as well. Not a big deal, but it's one more thing to do.
(We should really integrate this with the Struts core one of these days, so Daryl would have to scramble so hard to keep up, and Cactus would be less of an issue.)
Though, my favorite approach is to do conventional unit testing of the business objects, and then use Canoo WebTest <http://canoo.webtest.com> on the front end.
Canoo can't dig deep into the Struts internals the way Struts TestCase can, but it can test that you're pages are rendering and that the pages you expect render, all at the same time. It does need to key on more of the UI artifacts than Struts TestCase, but since it's configured from an XML file, it's much easier to keep it up to date. You need to have a web server running, but the tests execute *very* quickly.
If you're using Struts as an thin adaptor between your business layer and server pages, then JUnit and Canoo may be all you need. Though, complex Struts applications can still benefit from Struts TestCase.
HTH, Ted.
-- Ted Husted, Junit in Action - <http://www.manning.com/massol/>, Struts in Action - <http://husted.com/struts/book.html>, JSP Site Design - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
