Child pages
  • SoapUI Pro Functional Testing Plugin

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Plugin Information

View SoapUI Pro Functional Testing on the plugin site for more information.


A SmartBear plugin used to run SoapUI Pro tests from Jenkins builds.


  • The project you want to run must be saved in ReadyAPI version 2.1.0 or later.
  • The Jenkins node where you want to run your test must have ReadyAPI installed with an activated SoapUI Pro license. You can install and activate the license from a Jenkins build. To learn how to do that, see ReadyAPI documentation.

Important Note

Make sure you run Jenkins under the same user account you used to activate the SoapUI Pro license. Otherwise, you will get the "License not found" error. To learn how to fix this issue, see ReadyAPI documentation.


The build step has the following settings:

  • Path to testrunner - Specifies the fully-qualified path to the runner file (testrunner.bat or By default, you can find it in the <ReadyAPI installation>/bin directory.
  • Path to SoapUI Pro project - Specifies the fully-qualified path to the SoapUI Pro project you want to run.
  • Test Suite - Specifies the test suite to run. To run all the test suites of your project, leave the field blank.
  • Test Case - Specifies the test case to run. If you leave the field blank, the runner will execute all the test cases of the specified test suite, or, if you have not specified a test suite, all the test cases of your project.
  • Project Password - Specifies the encryption password, if you encrypted the entire project or some of its custom properties.
  • Environment - Specifies the environment configuration for the test run.

JUnit report

After the build is over, a JUnit-Style HTML report will be saved to the Jenkins workspace directory.

Also, you can view test results directly in Jenkins.

More information

You can find more information on how to use the plugin in ReadyAPI documentation.

  • No labels