[
http://jira.codehaus.org/browse/MNG-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MNG-591.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: Issues to be reviewed for 3.x)
Assignee: Benson Margulies
The last comment in here was years ago, inviting the OP to comment if the work
done was insufficient. There is no comment in all that time, so a close is
overdue.
> Integration tests lifecycle
> ---------------------------
>
> Key: MNG-591
> URL: http://jira.codehaus.org/browse/MNG-591
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Kenney Westerhof
> Assignee: Benson Margulies
> Priority: Blocker
> Original Estimate: 8 hours
> Time Spent: 45 minutes
> Remaining Estimate: 7 hours, 15 minutes
>
> 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?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
