there was a thread regarding this on the dev list quite some time ago where folks were kicking around what lvl of support and specifically how maven was going to support different lvls of testing. Unit tests are pretty well locked down by surefire, and integration tests (testing how different subprojects interact) has intermediate support in the core-it verifier that maven and a couple of other parts of maven use. I think vmassol even added some phases specifically for integration testing not too long ago.
Nice job putting this together though, I think the consensus from that email was to wait and see how the problem breaks down and gets solved and work it into maven more formally down the road :)
jesse
On 5/7/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
I believe there is certainly interest in plugins which can help
automate integration testing.
I for one would like to check it out and perhaps use it, depending on
my success at writing cactus tests. ;-)
Wayne
On 5/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi all,
> I wrote an integration test plugin. It:
> 1 compile file from the integration-test directory
> 2 cactify if necessary
> 3 deploy to test server(using cargo)
> 4 run the test
> 5 undeploy
>
> phase 1 and 3 are mostly cut/paste code from compiler/surefire plugin. I
> plan to send patch to those plugin so they compile/test IT directory but
> used that method as a workaround.
>
> I use this plugin with JBoss but it should work with any container
> supported by Cargo
>
> I will add DBUnit and JMeter(hopefully) capability.
>
> Alexandre Russel
>
>
--
jesse mcconnell
