Setup and Teardown Script Editors

Setup and teardown scripts exist on the level of test case, test suite and project. They are executed before and after the run of an entity, respectively.

The editors support all the standard features of ReadyAPI scripting editors such as property expansions, code validation, and code templates.

• Test case
• Test suite
• Project

Click the image to enlarge it.

Click the image to enlarge it.

Click the image to enlarge it.

Below is a list of the default objects that are available in the setup and teardown script editors:

You can see methods and properties of these objects on the Code Completion list. To invoke it, type the object name and press Ctrl+Space.

Object reference

To learn more about an object, find it in the API docs. API docs describe the internal structure of ReadyAPI; however, the names of objects used in the scripting editors are not necessarily the same as the names in the internal structure of ReadyAPI. To find an object in the documentation:

1. Use the getClass() method that every object in ReadyAPI has to find the class name.

2. Post the result to the Script Log using the log.info() method.

For example, for the context object the script will look like this:

Groovy

def className = context.getClass();
log.info(className);

Click the image to enlarge it.

Here are the links to examples of some scripts that can be run in the Setup and Teardown script editors:

• Access Properties

• Control Virtual Service Execution

• Log Results