[jira] Commented: (MNG-591) Integration tests lifecycle

["Kenney Westerhof (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-591?page=comments#action_45936 ] 

Kenney Westerhof commented on MNG-591:
--------------------------------------

I just committed sandbox/maven-it-plugin which has the ability to fork maven (sort of)
to run all projects found in src/it/. Use like this:

      <plugin>
        <artifactId>maven-it-plugin</artifactId>
        <executions>
          <execution>
            <phase>integration-test</phase>
            <goals>
              <goal>fork</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

Brett, can you see if this is a suitable solution for this issue? All setup/teardown/deployment/whatever
can now be done in the integration test projects. Test projects can depend on the parent project
(which could be added at runtime) so that they have access to the generated artifact (and test against it).

> Integration tests lifecycle
> ---------------------------
>
>          Key: MNG-591
>          URL: http://jira.codehaus.org/browse/MNG-591
>      Project: Maven 2
>         Type: Improvement
>     Reporter: Kenney Westerhof
>     Assignee: Brett Porter
>     Priority: Blocker
>      Fix For: 2.0-beta-2

>
> Original Estimate: 8 hours
>        Time Spent: 45 minutes
>         Remaining: 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org