About the directory lay-out; I was looking at a svn checkout of http://svn.apache.org/repos/asf/maven/plugins/trunk/ There seem to be it dirs in: ./maven-clover-plugin/src/it ./maven-surefire-plugin/src/it ./maven-dependency-plugin/src/it ./maven-antrun-plugin/src/it ./maven-assembly-plugin/src/it
Aren't these supposed to be executed automatically? I thought this "subproject" would use the actual project and test it. I suppose these are executed manually. Philippe On Mon, 2006-09-18 at 07:12 -0700, Wendy Smoak wrote: > On 9/18/06, Philippe Faes <[EMAIL PROTECTED]> wrote: > > > Is there an easy way to automatically build and test integration test > > projects? > > I have an integration test in: > > ./src/test/it/pom.xml > > The maven doc suggests this should be build and executed in the > > integration-test lifecycle, but > > $ mvn integration-test > > does not run my test. > > I'm not so sure about that directory structure. You have a pom.xml > file underneath 'src' ? > > I would expect something like: > project/core/ > project/webapp/ > project/integration/ > project/integration/src/test/java (<-- or src/it/java ) > > With the integration tests in a separate module, you can use the info > on the wiki page that Mykel linked to. You might need to add > <testSourceDirectory> if your test classes are not in the default > src/test/java directory. > > Another option is for the 'integration' module to use packaging type > 'pom' and for you to bind executions of all the plugins exactly where > you want them. > > In short, integration testing is not yet supported 'out of the box' > just by placing classes in the right directory. It's still under > discussion, and for now you have to add some configuration. > -- Philippe Faes <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
