07 November 2008 - 2.5-beta2 |
Prior to using the plugin, add the eviware maven 2 repository either to your project or settings.xml;
<pluginRepositories> <pluginRepository> <id>eviwarePluginRepository</id> <url>http://www.eviware.com/repository/maven2/</url> </pluginRepository> </pluginRepositories>
Then, add the soapUI plugin to your pom.xml
<plugins> <plugin> <groupId>eviware</groupId> <artifactId>maven-soapui-plugin</artifactId> <version>1.7.6</version> <configuration> <projectFile>sample-soapui-project.xml</projectFile> <host>http://127.0.0.1:8181</host> </configuration> </plugin> </plugins>
Run functional tests with
mvn eviware:maven-soapui-plugin:test
loadtests with
mvn eviware:maven-soapui-plugin:loadtest
and MockServices with
mvn eviware:maven-soapui-plugin:mock
The plugin will load the specified project file and run all TestCases available in all TestSuites. If you
want to narrow down which TestSuites/TestCases/LoadTest to run, use the testSuite
,
testCase
and loadTest
properties for that purpose.
If you configure any of the integrated code generation tools in soapUI for an interface in your project, you can invoke this code generation functionality with
mvn eviware:maven-soapui-plugin:tool
which could be configured in the maven 2 build process as part of the generate-sources step:
<plugins> <plugin> <groupId>eviware</groupId> <artifactId>maven-soapui-plugin</artifactId> <version>1.7</version> <configuration> <projectFile>sample-soapui-project.xml</projectFile> <testSuite>OleTest</testSuite> <iface>IOrderService</iface> <tool>wsi,axis1,axis2</tool> <settingsFile>C:\workspace\core\soapui-settings.xml</settingsFile> </configuration> <executions> <execution> <phase>generate-sources</phase> <goals> <goal>generate</goal> </goals> </execution> </executions> </plugin> </plugins>
Several tools can be specified in a comma separated list, so the above example would run both WS-I reports and configured code generation for both Axis1 and Axis2. Also, the soapUI settings file has been specified since it contains tool paths and global WS-I settings