The SoapUI plugin provides a means to run SoapUI test suites and load tests defined in SoapUI project files. The entire project must be present, not just an exported test. It must contain one or more test suites, with one or more tests cases or load tests.
The SoapUI plugin has been tested with SoapUI version 5.1.3, 5.2.0, and 5.2.1 running on Windows and Linux Endpoints.Test runner runs best with version 5.1.3, but the test results will be identical across the versions of SoapUI. SoapUI Pro is not required.
SoapUI should be run manually at least once on the endpoint before running it with the plugin. This is necessary to choose whether or not to accept sending usage information to the developers. If you don't run it once first, the plugin operations will hang. This indicates the need to run it manually.
You can install SoapUI on your Build or Development servers for execution of Tests. This should be defined in FlexDeploy as Testing Instance. See Creating/Editing a Test Instance. You can use this Testing Instance as Override on your Test Definition, which means that if you are running Build or Deploy on any server/environment and as part of the Workflow you execute tests, execution will transfer to specific Testing Instance for execution of Tests.
Make sure to Disable Usage Statistics as shown below on SoapUI installation.
Don't have a SoapUI installation available for FlexDeploy? No problem. All you need is a docker install and you can make use of our SoapUI plugin for running on Docker.
The SoapUI Docker plugin functions exactly the same as the traditional java based SoapUI plugin with the notable exception that it needs to be run on an Endpoint that is configured as a Docker Host or a K8s cluster.