I thought about this a little more and have some ideas about what I'd
like..... I dunno if this is remotely possible.
- keep the test app and test code close together in svn. It's going
to be a lot easier to work with a single test if these are close
together, rather than like the testsupport stuff that is far from the
tests that use it.
- make it easy to run the tests on a single app... so there's an easy
way to build the test app, start up a server, and run the tests for
that app.
- make it relatively quick to run all the tests.... which I think
means starting a server, then for each app, deploying, running tests,
and undeploying. My current understanding of what we have now is
that the server is going to be started and stopped for each app if
we've set things up for my second requirement :-)
thanks
david jencks
On Dec 8, 2006, at 1:21 PM, Prasad Kashyap wrote:
I know what you mean. I just worked on the app that David was talking
about those do need a separate module by themselves. I didn't realise
his scenario until I saw the JIRA.
I was talking about something like
testsuite/web-testsuite/test-servlet25. This example builds a war and
tests it in the same pom.
Cheers
Prasad
On 12/8/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
On Dec 8, 2006, at 6:30 AM, Prasad Kashyap wrote:
> 1) just make a copy of test-deployment, (say call it cxf-
deployment)
> 2) use it's child profile to go thro the complete maven lifecycle -
> compile, build and test your apps.
> 3) it's parent (deployment-testsuite) will take care of the server
> start/stop and reporting for you.
This won't actually work as easily as you may have imagined Prasad.
To effectively build some apps, you actually need to have them live
in their own module, so that they can be built using the associated
maven plugins.
I do not believe that the current testsuite setup takes this into
account... and this is why I think it is premature to simply roll out
the same config/layout with out having some more real tests, which
build these test applications and allow for effective organization.
I don't think we are quite there yet... close, but still a bit off.
--jason
