oopps ... cross posting ...
>As to testing requirements, the obvious starting points are Junit,
>J2EEUnit, and HttpUnit.
>
>< http://junit.org/ >
>
>< http://j2eeunit.sourceforge.net/ >
>
>< http://sourceforge.net/projects/httpunit >
>
>To the extent possible, we should try an integrate testing with Ant.
>This could lead to a gump that not only builds code, but tests it as
>well.-)
>
>
>-Ted.
I have posted a message saying I am willing to donate J2EEUnit to Apache if
it helps.
Also, I have already created Ant scripts that automate J2EEUnit testing with
several Servlet Engines. My Ant scripts has test-xxx targets (where xxx is
the name of the servlet engine) which does the following :
- start the servlet engine,
- run the J2EEUnit/JUnit tests,
- stop the servlet engine
where xxx is for the moment = {Resin 1.2, Resin 1.3, Tomcat 3.1.1, Tomcat
3.2.1, Tomcat 4.0, Orion 1.4, WebLogic 5.1}
In order to be able to do this I had to create an Ant target (called
startserver) which calls an Ant target (the target that should start the
server) in another thread and waits for the server to be started (by trying
to connect to it on a specified URL)...
Look at
http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/j2eeunit/build/build.xml?rev=1
.18&content-type=text/x-cvsweb-markup&cvsroot=j2eeunit if you want to check
my Ant build.xml file.
So I guess integration with Gump should be a breeze ... :)
Thanks.
Vincent
