At 06:45 PM 6/18/2001 +0100, Vincent Massol wrote:
>There is no choice. Cactus has chosen to use option 2 and *not* option 1.
>The assumption table was jsut to explain the thought process that led to
>Cactus' architecture. The architecture is described below.
>
>Now, it is really very simple. Have a look at
>http://jakarta.apache.org/commons/cactus/using.html which is really a
>tutorial that explains how to write test cases. You only need to look at the
>architecture part if you want to understand how Cactus works internally.
The one thing that is not clear from this documentation is how you actually
run the tests and where you find the results.
It seems reasonable to assume that you have to deploy your tests as
servlets and invoke them from a web browser, seeing
the results displayed there.
