I figured it out:

add
        <skipTest>false</skipTest>

to the main plug-in configuration.  This will tell flexmojos to not
run the test-run goal in the default test phase.

Then add a new configuration that sets skiptest to true.


                                        <execution>
                                                <!-- Bind Flexmojo's test-run 
goal to the build lifecycle's
integration-test phase -->
                                                <id>integration-test-run</id>
                                                <phase>integration-test</phase>
                                                <goals>
                                                        <goal>test-run</goal>
                                                </goals>
                                                <configuration>
                                                        <!-- Undo skipping of 
tests that was set by default in main
configuration -->
                                                        
<skipTest>false</skipTest>
                                                </configuration>
                                        </execution>

It undocumented, but apparently <skip> means skip created the final
artifact and <skipTest> didn't do anything that I could detect.  Use
<skipTests>



On Oct 27, 10:16 pm, David Vree <[email protected]> wrote:
> I have some FlexUnit4 integration tests that need to a servlet
> container to start up for the tests to execute.  Normally I would use
> the Cargo plugin to Maven for this and bind executions like so:
>
>     <executions>
>         <execution>
>           <id>start-container</id>
>           <phase>pre-integration-test</phase>
>           <goals>
>             <goal>start</goal>
>           </goals>
>         </execution>
>         <execution>
>           <id>stop-container</id>
>           <phase>post-integration-test</phase>
>           <goals>
>             <goal>stop</goal>
>           </goals>
>         </execution>
>       </executions>
>
> However, I noticed that Flemojos's binds it's test-run goal to the
> build lifecycle's "test" phase rather than the integration-test
> phase.  I think this makes sense since FlexUnit is probably more often
> used for unit testing than integration testing.  But how would I go
> about unbinding the test-run from the test phase and rebinding it to
> the integration-test phase.
>
> There is no pre-test or post-test phases or I could just start/stop my
> container with those...

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to