Readyapi documentation

Readyapi documentation DEFAULT

Testing using SoapUI / ReadyAPI

In this tutorial, we will use some tests specified in SoapUI / ReadyAPI, which supports out-of-the-box JUnit reports.

This example is based on the sample SOAP project that is available upon SoapUI installation.

The "SOAP Sample Project" from ReadyAPI v1.9.0 contains 3 TestSuites with a total of 11 test cases. 

After running the tests (either from the UI or from the command line) and generating the JUnit XML reports (e.g., report.xml), it can be imported to Xray (either by the REST API or through the Import Execution Results action within the Test Execution).

From the UI,

or from the command line:

sh -c ./ -j -J -f/tmp/soapui "-RProject Report" "-EDefault environment" SOAP-Sample-Project-soapui-project.xml

Each Test Case is mapped to a Generic Test in Jira, and the Generic Test Definition field contains the name of the project concatenated with the name of SoapUI's TestSuite and the name of the test case in SoapUI.

The Execution Details of the Generic Test contains information about the context, which in this case contains the name of the project and the name of SoapUI's TestSuite.


ReadyAPI Functional Testing


A SmartBear plugin used to run ReadyAPI functional 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 ReadyAPI Test 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 ReadyAPI Test 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 /bin directory.
  • Path to ReadyAPI project - Specifies the fully-qualified path to the ReadyAPI 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.
  • Test Suite Tags and Test Case Tags - Specify which tags must contain the test suite or test case to be run. To create complex conditions, use the (logical OR), (logical AND) and (logical NOT) operators.
  • 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.


After the build is over, the plugin creates the following reports:

  • A printable PDF report, which is published to Jenkins. To view it, open the build page you are interested in and select ReadyAPI Test Results on the left. Also, the link to the report is available at the end of the Console Output log.
  • A JUnit-Style HTML report, which is available in the Jenkins workspace directory.
  • A JUnit report, which is published to Jenkins. To view it, open the build page you are interested in and select Test Results on the left.

More information

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

Version history

Version 1.7 (July 21, 2021)

  • New feature: Added the possibility to use EnvVars for TestRunner and project file paths.
  • Fixed: Project execution sometimes hung on a slave machine.

Version 1.5 (June 24, 2020)

  • Fixed: The test case report could not be generated when a single test case was run.

Version 1.4 (April 10, 2020)

  • Fixed: A security vulnerability in project password storage.

If you update to version 1.4, to ensure the security of your passwords, you need to do the following for all the jobs that use the plugin:

  1. Select a job and click Configure.
  2. Save the configuration without making any changes by clicking Save or Apply.

Version 1.3 (February 7, 2020)

  • Fixed: In some cases, a job with a composite project could not be run.

Version 1.2 (December 13, 2019)

  • New feature: Support for tags.

Version 1.1 (August 7, 2018)

  • New feature: A printable PDF report is now published to Jenkins.
  • Fixed: When a test failed, the build was not marked as failed.
  • Fixed: JUnit reports were not published if the build was run on a slave computer.
  • Fixed: The optional fields were required in the Blue Ocean UI.

Version 1.0 (June 5, 2018)

  1. Fraternity hoodies
  2. Hiawatha trail reviews
  3. Old xian comics
  4. Dalton self storage

ReadyAPI is a cross-platform solution for advanced web service testing. You can use it to rapidly create and run automated functional, load, regression, security and compliance tests for your web applications.

It supports all the standard protocols and technologies, from SOAP- and REST-based web services to JMS enterprise messaging layers, databases and Rich Internet Applications. It also offers web service inspection, simulation (mocking), assertions, HTTP traffic recording, security scans, Groovy and JavaScript scripting, and much more.

To learn more about ReadyAPI, visit our web site:

How ReadyAPI Can Help You With Testing

ReadyAPI can greatly enhance your web service testing experience. Using ReadyAPI you can –

  • Facilitate multi-platform opportunities in your organization and create and run functional and load web service tests on Windows, Linux and Mac OS.

  • Test RESTful and SOAP-based web services.

  • Check how your APIs work under a massive load.

  • Scan your web service for security vulnerabilities, such as SQL injection, XML bombs, cross-site scripting, invalid input data and so on.

  • Use web service mocking to create tests for web services that are not live yet, for applications that use third-party web services and so on.

Try ReadyAPI Pro for Free

See Also

Other Tools That Help You Test Better
Integration With ReadyAPI and SoapUI

Teamwork, and Git Integration - API Testing With ReadyAPI

The wardrobe has changed, the hairstyle has changed, the roundness of the figure has changed, the behavior has changed. the girl from the last story, stuck in adolescence, frowning and gloomy, fighting with the whole world, expecting nothing good from life and surroundings, has turned into.

A young charming woman. And she took even my compliments to this amazing metamorphosis for granted, without much embarrassment.

Documentation readyapi

Several times I heard sounds that looked like laughter and crying at the same time. Did Valentina really give. Well, of course, theres no husband, its hard for her alone, the womans in the very juice, I suppose she wants. Doubts and uncertainty all overcame me. Finally, I could not stand it and with an uncertain, creeping gait, I moved towards the barn.

Logging and Reporting - API Testing With ReadyAPI

Alas, in the afternoon we parted. I think their names are not real, I did not remember the numbers of their cars - I almost forgot my address. Then, let alone remember the number of some car. Ill hardly find their house either.

You will also be interested:

She was wearing a strap-on. With them, she began to penetrate the girl. Natasha started making sounds.

1572 1573 1574 1575 1576