Hi Aaron, Thanks for reminding me. Instructions on using this is needed even because it uses some bleeding edge Maven features :-) It uses yet to be released maven-site-plugin and maven-default-skins. So some amount of setup has to be done. Now that you have expressed interest, writing the doc for others to use it has jumped up the priority list. But before that a small instruction set will be posted here soon.
The itests currently has some 6 testcases. They are - start/stop server, deploy/undeploy module start/stop module. They have are all wriiten as mojos. These mojos execute during the "integration-test" phase of the m2 cycle. The instructions will use those as examples if you choose to write & plugin your own mojo. We should soon have a test using junit and bound to the "test" phase of the m2 cycle. That will also make a good example. Cheers Prasad On 2/24/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: > Can you post some instructions on how to add tests to this? There are > a lot of places I've skipped tests because it required too much of the > server to be running. > > Thanks, > Aaron > > On 2/24/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote: > > Thanks to Mavens, Jason & Brett and Geronimo's Davids, Jencks and > > Blevins, the itests which were under OpenEJB earlier has now been > > converted to Maven2. It has also been enhanced to perform integration > > tests on other components and services. Other itests can now simply > > plug in their tests into this framework. When we move completely to > > Maven2, it can also be invoked during the integration phase of our > > build in our gbuild setup. > > > > Currently this setup is a basic testing infrastructure with a set of 6 > > test cases. More test cases can be plugged into it by anybody. > > > > From here, we could go just about anywhere. Some of the things we could do > > are : > > - plug in the openejb itests from the old maven1 build. > > - documentation about the itests subproject. > > - documentation for others to write and plug their own tests. > > - hook it up with Continuum for gbuild. > > - some simple feature enhancements & cleanup. (some maven JIRAs have > > been opened for this). > > - publish results. awaiting a maven feature yet to be released - > > maven-default-skin. > > - (your idea goes here) > > - (your idea goes here) > > - > > - > > > > > > More ideas and participation in this are most welcome. > > > > Jacek, should I open a JIRA for this as a subtask under the M2 > > conversion effort ? Or should we keep this separate ? > > > > Cheers > > Prasad > > >
