A test suite is a collection of test cases that can be used for grouping functional tests into logical units.
Your project can contain any number of test suites and you can see and execute them all in sequence or parallel (see Test Suites).
 |
The test suite toolbar contains quick access to the most frequently used commands.
 |
The main purpose of the Test Cases page is managing test cases. To learn how to do it, see Managing Test Cases.
The Test Cases page gives you an overview of the contained test cases and their run status. It allows you to add, remove or modify test cases, as well as assign tags and use them to filter test cases for a test run. For more info, see Working with Tags.
Besides that, panels of the page allow you to modify various test suite aspects:
Description – Specify the text description of the test case.
Properties – Manage the list of test case properties. See the Test Suite Properties section.
Setup Script – Specify a script that is run at the start of a test case run. To learn more, see Setup, TearDown, and Report Scripts.
TearDown Script – Specify a script that is run when the test case run finishes. To learn more, see Setup, TearDown, and Report Scripts.
Report Script – Specify a script that is run when you generate a report. To learn more, see Script Extensions.
Report Parameters – Manage the list of parameters used for the report creation. To learn more, see Script Extensions.
To learn about | See |
|---|---|
Transaction Log | |
Compare | |
History | |
Coverage |
Besides editor panels, you can adjust test case behavior by using its properties in the property tabs in the Navigator.
Name | Description |
|---|---|
Name | The name of the test suite. ImportantSpecial characters in the name, including (but not limited to) |
Custom Test Suite Properties tab in the Navigator and the Properties panel in the test suite editor, you can create any number of properties. These properties are available to child test cases and other test suites in your project. To manage the property list, use the toolbar:
Custom test suite properties can be stored locally in your workspace file by selecting the checkbox on the right. To learn more about it, see Locally Stored Properties .
Tags help you group test cases within a test suite. You can run only the tests containing tagged test cases. Also, you can exclude test cases with specific tags from the test run. Tags are always alphanumeric.
You can edit all tags in the project from the Tags tab in the Project editor.
Select the test case.
Click
on the toolbar.Specify the name of the tag and press Enter. The specified tag will be added to the selected test case.
 |
Select the test case.
Click
on the toolbar.Remove the selection of the tags you do not need. These tags will be removed from the selected test case.
 |
Open the list of selected tags.
To include the tagged test cases to the test run and exclude others, select from the Show/Hide drop-down menu.
Select a filtering rule:
Select to show test cases only with all the selected tags. For example, if you select and , ReadyAPI will only show test cases that contain both and .
Select to show test cases with any of the selected tags. For example, if you select and , ReadyAPI will show test cases that contain either , , or both.
Select the tags you need.
 |
Open the list of selected tags.
To exclude the test cases from the test run, select from the Show/Hide drop-down menu.
Select a filtering rule:
Select to show test cases only with all the selected tags. For example, if you select and , ReadyAPI will hide only test cases that contain both and .
Select to show test cases only with any of the selected tags. For example, if you select and , ReadyAPI will hide test cases that contain either , , or both.
Select the tags you need.
 |