Our actual testsuite for JBossAS starts and stops different server
configurations 15-20 times as well as starting up clusters of servers. From
what I can see, to do this the maven way, I would need 15-20 integration
projects which would be executed by hand or cruise control or 1 integration
project with 15-20 profiles executed in the same fashion as above. Neither
one of those solutions provides the same level of functionality as what I can
achieve using ant.
Another key point I have to deal with is simply the migration and the user
experience.
Currently they can go into our testsuite and issue: ant tests
At which time our entire testsuite will run, performing integration testing for
all configurations. I can't take away that functionality.
SO....to achive this, it sounds like I need to write a plugin which allows many
executions, where
For each execution
a) configure server and start it
b) deploy app
c) run unit tests
d) undeploy app
e) stop server
Having not done this, I am giving you theory, but I believe that you
don't need to create 15-20 integration test suites and you don't need
to create your own plugin.
By using pom packaging, there are no plugins bound to the lifecycle.
So you are free to bind any plugins to any part of the lifecycle and
define your own.
So if you bind your stuff to "integration-test" and run mvn
integration-test then the only thing that will run is what you have
bound.
Then you need to setup 15-20 different executions of the same sets of
plugins, one for each environment. Admittedly it is probably going to
be a lot of cut and paste, but it is all defined in the one pom and
you can see in which order things will run. Now each execution will
run against all the same integration tests defined in the current
project.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
