maven-soapui-extension-plugin

This plugin adds new features and bug fixes to SmartBear plugins: soapui-pro-maven-plugin and soapui-maven-plugin.
For more information about how to use it, see the wiki.

Last released version: 4.6.4.1 (16-May-2014) available on Maven Central

News (2014-10-07)

Latest version is now quite old. For the summer, I have been working to implement 5.x support but work is currently paused because of dependency issues (javafx, missing dependencies in 5.1.x)

So, I am currently focusing on a new version on the 4.6.4 line. As major new features, it will contain

new custom junit report for both OSS and PRO (see #42 and #56)
mock-as-war support for all maven 2.2.1+ versions (see #70 and #121)

Hope you will enjoy

Main features

Documentation

give tips about maven plugin configuration (both for maven-soapui-extension-plugin and SmartBear plugins)
provide full documentation of goals and parameters

New features

general
- only one plugin for both SoapUI OSS and PRO support (SmartBear provides 2 plugin implementations)
convert-project additional goal
- convert-project converts composite to standard projects or standard to composite projects
mock goal
- add several parameters to activate and control the coverage report generation when using the pro runner
- the runnerType parameter lets choose to use the open source or pro runner
mock-as-war additional goal
- mock-as-war generates war file (and/or exploded war) that contains the mockservices defined in the SoapUi project as this can be done from the GUI
test goal
- the junitHtmlReport parameter lets disable junit html report generation when using the pro runner
- the runnerType parameter lets choose to use the open source or pro runner
- the testsuiteProperties parameter lets override custom properties in test suites
- configure the JunitReportCollector to be able to modify xml junit files generation
test-multi additional goal
- test-multi allows to run several projects in the same plugin execution. Choice of projects to be runned is done by scanning one or several directories and selecting which projects to include/exclude
test-verify additional goal
- test-verify lets user run soapui tests, perform post processing tasks and then fail the build if some tests have failed. This is very usefull to run multiple projects

Improvements

test goal
- by default, logs are generated in a subdirectory of ${project.build.directory} see the logs documentation
- do not display details of errors as exception stack trace to avoid flooding of the maven console, see #2
mock goal
- by default, logs are generated in a subdirectory of ${project.build.directory} see the logs documentation

Bug fixes

almost all SmartBear plugin versions have missing dependencies. This is fixed in maven-soapui-extension-plugin, see the dedicated dependency issues page
fix the 'groovy.log' bug even in pre SoapUI 5 versions, see the logs documentation
mock goal
- make the 'skip' parameter work, see #35
- append groovy log messages only once in the console, see #68
test goal
- append groovy log messages only once in the console, see #68

Tests

SmartBear maven plugins have almost no tests. Have a look on the soapui-maven-plugin-tester.

maven-soapui-extension-plugin has both unit tests and high-level tests. These high-level tests are

executed with the maven-invoker-plugin, this means that these tests are runned with maven plugins on real soapui projects
created to show bug or missing feature in SmartBear implementations
created to show fix, improvement or feature in maven-soapui-extension-plugin

Roadmap

Short term

support SoapUI 5.0.0, 5.1.0, 5.1.1 and 5.1.2
improve the test-multi goal to run multiple soapui projects. See opened issues
provide a new JunitReportCollector to have more details about failures (steps, assertions) in the junit report. See #42

Mid term

improve the mock-as-war goal for generating war from mock services. See opened issues
have a specific implementation for the security-test goal and implement improvements. See opened issues

Long term

found a way to make report generation work without having a SoapUI installation (PRO feature)
add a goal to export wsdl interface from a SoapUI project
does not rely on SmartBear maven plugin

Supported java and maven versions

maven 2.2.1, 3.0.x (tested with 3.0.5), 3.1.x (tested with 3.1.1) and 3.2.x (tested with 3.2.1 and 3.2.3)
java 6 and 7 (soapui needs java 6+ as of version 4.0.0), java 8 experimental support

CI Build status

If it is not specified, the CI job

only builds the master branch
uses a shared local maven repository across builds
is runned
- once a day if code modification occurs
- on Linux OS

List of CI jobs

maven 3.2.3, openjdk6, openjdk7, oracle jdk7 and oraclejdk8 (Travis) - builds all pushes in all branches and pull requests, uses a fresh maven local repository at each build
maven 3.2.1, openjdk8 (CloudBees)
maven 3.2.1, oracle jdk6 (CloudBees)
maven 3.1.1, oracle jdk8 (CloudBees)
maven 3.1.1, oracle jdk7 (CloudBees)
maven 3.1.1, oracle jdk6 (CloudBees)
maven 3.0.5, oracle jdk8 (CloudBees)
maven 3.0.5, openjdk8 (CloudBees)
maven 3.0.5, oracle jdk7 (Buildhive) - builds master and pull requests, uses a fresh maven local repository at each build
maven 3.0.5, oracle jdk6 (CloudBees)
maven 3.0.4, openjdk7 (drone.io) - only launched manually, uses a fresh maven local repository at each build
maven 2.2.1, openjdk8 (CloudBees)
maven 2.2.1, oracle jdk6 (CloudBees)
maven 2.2.1, oracle jdk7 (CloudBees)