I think that the Manual Cactus Integration page is not explicit enough regarding running in-container test on an container that is not configured by Cactus. The Tomcat Quickstart gives an example test and runs the test using the browser method. The brief command-line example demonstrates running tests with TestRunner. The Ant examples all use the Cactus ant tasks (and state that runservertests calls a JUnit task).
Looking back over the Cactus site, all the information is there but in separated parts that you need to pull together to realize it. I guess I didn't make the connection that to run tests using Ant, you can use the JUnit task (if the container is configured properly) and that the runservertests task is really a wrapper that starts/stops the container and runs that JUnit target in the middle. If I had any suggestion to make out of all this, it would be to reorganize some of the Running Tests docs along the lines of use cases instead of laying out all of the available options (which can be overwhelming to a new user who just wants to get up and running without knowing the full details of how it works under-the-hood or what all the available options are)... 1) Running tests in an existing already-configred container * How to configure the container (combine the server-side config/classpath pages and link to container-specific pages like Tomcat, Jetty, etc) * How to configure the client (combine the client-side config/classpath pages) * How to run tests ** JUnit TestRunner examples ** Ant example with a JUnit task ** Browser examples (with and without XSLT) 2) Running tests in a container managed by Cactus * cactifywar * cactus example * runservertests * webxmlmerge 3) Running tests in an IDE * Eclipse * etc etc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
