Yes, it is simply a matter of editing the main BVT test to add extra junit tests.
We use a servlet to run our tests in a j2ee environment. We got the code from here: http://www.javaworld.com/javaworld/jw-05-2000/f_jw-0526-testinfect.html although we had to make some changes to spit out XML instead of HTML, i think. Then our master build script just starts up the server, connects to the servlet using an URLConnection, saves the xml response to a file, and then shuts down the server. Matt Foemmel ThoughtWorks, Inc. Barrie Treloar <[EMAIL PROTECTED] To: [email protected] ch.com.au> cc: Ant Developers Mailing List <[EMAIL PROTECTED]> Subject: Re: martin fowler paper on continuous integration 09/20/2000 01:51 AM Please respond to ant-dev BVT: How do tests get added to the BVT. Is it simply a matter of editing the main BVT entry point and adding the extra junit tests? I'd also be interested in how you run your tests in a J2EE environment. How do you unit test when it depends upon the J2EE environment? Do you write test session beans in order to provide an entry point into the system? I've not given this enough thought yet but this seems a reasonable way to go. A greater discussion of how the tests interact with the build would be useful. The problems with testing in a J2EE environment has slowed down the introduction of automated testing and this is causing me concern as I would like being used.
