[MNG-591] Integration tests lifecycle

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Component/s: Plugins and Lifecycle
• Assignee: Benson Margulies
• Reporter: Kenney Westerhof
• Created: 14/Jul/05 15:32
• Updated: 19/Jun/11 16:39
• Resolved: 19/Jun/11 16:39

Description

I'm trying to do an integration test that depends on a war/ear to be deployed.

What i'm missing is:

• integration-test-compile stage and/or:
• a way to specify an integrationTestSourceDirectory or multiple testSourceDirectories in the pom

I can't put the test sources in src/test/java because then surefire will run them in the test stage, when
there's no artifact to deploy yet.

[Btw, I'm doing this while creating a cactus plugin, for the moment using cargo in the TestSuite itself to deploy.]

The idea is that the integration test sources go in src/itest/*; that there be a integration-test-compile,
integration-test-package and/or integration-test-appdeploy[or something] and that surefire
is also bound to integration-test.

Maybe something can be done using the src/test/project/some-project/.... approach seen in
maven-javadoc-plugin, maven-site-plugin and maven-eclipse-plugin (i'd like to see some of that
standardized anyway to allow plugin testing generally - which can also be seen as integration testing).

Thoughts, comments, approaches?

Issue Links

• depends upon: MNG-1628 Create new phase to prepare for integration tests
• is duplicated by: MNG-2344 Support for functional/integration tests is *way* too limited
• is related to: MNG-475 add integration-test scope