Versions Compared

Old Version 16

changes.mady.by.user Tristan Butzine

Saved on

compared with

New Version Current

changes.mady.by.user Tristan Butzine

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

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.

Tip

Setting up Testing Instance

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.

Key Features

  • Use existing SoapUI test suites and load tests

  • Aggregates test results for each execution

...

Code Block
# change path appropriately
/opt/SmartBear/SoapUI-5.5.0/bin
# /var/tmp will be where output will be written
./testrunner.sh -rjf /var/tmp <project.xml file name>
Tip

You will notice some errors during execution due to the fact that SoapUI installs some plugins during first invocation of testrunner. Once you execute SoapUI project file, go to home folder and delete plugins folder from .soapuios. Here are commands for Unix.

  • cd $HOME

  • cd .soapuios

  • rm -rf plugins

SoapUI Docker Plugin

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.

...