>My only concern is that the test *must* pass every time it is run, meaning
>that if you rely on this container behaviour, we need to define a test
>server (or several but well defined).
I'm not aware of any "test server" upon which this test webapp and/or test
suite will fail. (Well Tomcat 3.2 doesn't support "options", but the test
webapp doesn't rely upon it). So for now the "well defined" test server is
*any*. If you find one for which that is not case, we should certainly make
a note of it.
>We could even automate deploying the webapp, start the server and stop the
>server (I have done that countless times on Cactus so I could help with
>this automation).
If you'd find that helpful, feel free. Currently I just use:
ant -Dtest-webapp.dest=/path/to/catalina/webapps compile.test-webapp
and bounce the engine manually when the server-side of the tests change
(which isn't that often), and found that sufficient.
> > I'd welcome adding some (even dozens of) mock-object > based tests to
>the suite, but I'd be opposed to > removing the existing functional tests,
>as I
> > think they serve a useful purpose as well.
>I'm of course +1 to keep all existing functional tests !
So we're all in agreement. Go for it.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
