Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Using Selenium for functional testing of webapps, with Maven

The following profile comes from the parent pom for the Apache Shale example apps.

See this page for more information:

With Maven 2.0.4, putting both plugin executions in the process-resources phase did not work-- they were executed in the wrong order and so the build failed as Selenium had not yet been unzipped when antrun tried to copy the files. Moving the dependency-maven-plugin execution to generate-sources fixed the problem, but this should not have been necessary. See

No Format
                        <copy todir="${}/${artifactId}/selenium/core">
                           <fileset dir="${}/selenium/core"/>
                        <copy todir="${}/${artifactId}/selenium/tests">
                           <fileset dir="${basedir}/src/test/selenium"/>

Using Selenium Maven Plugin and Cargo

Tutorial at Functional testing with Maven, Cargo and Selenium by Carlos Sanchez

Examples at Continuum web tests, Archiva web tests, and the Maven Web UI Tests.