The focus in Ready! API is the project, but it is valuable to have an understanding of the various components that make up a testing solution. This section describes the various parts for reference purposes.

Ready! API Structure


Ready! API is a family of tools, combining all aspects of API testing into one solution.

→




Interfaces are the foundation for Ready! API projects. They are created from API service definitions.

→


REST Parameters

REST parameters are part of REST requests, and are configurable on Method and Request level.

→



A TestSuite is a collection of TestCases that can be used for grouping functional tests into logical units. Any number of TestSuites can be created inside a project to support massive testing scenarios.

→


A TestCases is a collection of TestSteps that are assembled to test some specific aspect of your service(s). You can add any number of TestCases to a containing TestSuite and even modularize them to call each other for complex testing scenarios.

TestCases are part of TestSuites and contain the TestSteps to be performed. Settings on TestCase level apply to the TestCase itself and all contained TestSteps, unless they have their own settings.

→


TestSteps are the “building blocks” of functional tests in SoapUI. They are added to a TestCase and used control the flow of execution and validate the functionality of the service(s) to be tested.



The full hierarchy provided by Ready! API starts with the TestStep module which contains the logic for assertions authorization, and very much more. It is easy to map these modules to conceptual steps in your testing, to get a clearer grasp of what is going on.

TestStep Organization

TestSteps are the core building blocks of functional tests.

Each TestStep performs some step for validating the functionality to be tested. TestSteps are by default executed sequentially, but several possibilities exist for branching, looping and even calling other TestCases, making complex testing possible when required.

Any number of TestSteps can be added to a TestCase.

TestSteps can be cloned or moved to other TestCases in the current Workspace. If the target TestCase is not in the same Project and any corresponding interfaces are not available in the target project, you are asked to also clone the interfaces as well.

Data Sources

Data Sources allow you to get data from different external storages or generate the data during the test run.

You can use data sources in data-driven testing in both SoupUI NG to populate testing properties and in ServiceV to generate service's response.

Settings of each DataSource depend on DataSource type. Several data sources are available only in the SoapUI NG.

Data Source ServiceV SoapUI NG Description
DataConnection + + Gets data from a database by using a JDBC connection. It similar to the JDBC data source, but it uses predefined JDBC database connections.
Data Generator + + Generates data by using built-in data generator engine.
Excel + + Gets data from the excel tables.
File + + Obtains content of the specified file line by line.
JDBC + + Gets data from a database by using a JDBC connection. Unlike Data Connection data source, it uses connection specified in the data source.
Grid + + Obtains data specified in a grid.
Groovy - + Generates data by using groovy script.
JSON - + Parses the desired data from the JSON content by using JSONPath.
XML - + Parses the desired data from the XML content by using XPath.
Directory - + Iterates through the specified directory and gets file content.

→


Assertions are an important part of validating your service. This section provides a reference of the various assertion types available in Ready! API.

→


Ready! API contains a number of logs for various purposes.

→

Help and Feedback

You did not find what you looked for?

© 2016 SmartBear Software

Didn't find an answer? Try searching here: