[EMAIL PROTECTED] wrote:
I don't use the Jasper task for the development environment
though, because one wouldn't mind a negligible wait for just
one JSP page in the development environment and
also because the Jasper task takes a very long time to
complete, it is not suitable for a dev build but only for
production build.
I do what John suggests and use HttpUnit.
1. you need those tests anyway
2. you can fetch all pages, including error pages and those that need
auth (if your tests log in first)
3. you can also walk every link from the index page and verify
you have
no broken links
4. Tests are independent of the jsp-container ;-)
5. You get to verify the output matches what you want. Except Httpunit
feeds its stuff through tidy; its very HTML-centric. Does anyone know
how to use it to test proper XML documents, with namespaces and the like?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
