Manage multiple test suites

You can add multiple test suites per project and run them in sequence. This is especially useful when collaborating with others.

Create a new test suite

To add a test suite to an existing project, follow the instructions below:

In the dialog that appears, verify that Test suite is selected as the template.

Name the test suite.

Click Create.

Result(s):

The new test suite appears in the project view. Usually, it also opens automatically in the test suite view.

The newly added test suite in the projects view.

The test suite tabs below the Ranorex Studio toolbar.

Cut/copy/paste/delete/move multiple test suites

To ensure the integrity of your project, you cannot cut, copy, or paste an entire test suite. However, you can delete and rename test suites. Select a test suite in the project view and open the context menu to use the delete and rename options:

• An entire test suite cannot be cut, copied, or pasted.
• Similarly, you can’t move an entire test suite to another project.

Delete, Rename

• Test suites can be deleted.
• Test suites can be renamed.

Set the test sequence

Once a project contains at least two test suites, you can specify a sequence for the test suites.

• If you have multiple projects with multiple test suites, select the project to configure here.
• By default, the current test project is pre-selected.

Use the order buttons on the left to change the position of the test suites in the test sequence.
Use the ON/OFF buttons to exclude selected test suites from the test run.

Manage the test sequence file and parameters

This section introduces the configuration file where the test sequence is stored and describes how to add test suite run parameters to this file.

Test sequence file

When a project contains at least two test suites, a test sequence file with all configuration information is created automatically and added to the project folder.

Test sequence file content and syntax

• [ ] enclose the test sequence file
• { } enclose all configurations for one test suite
• Multiple test suites are separated by a , (JSON formatting syntax)
• Configuration arguments follow the syntax "":""
• Multiple parameters are separated by a ,

Adding command line arguments

Command line arguments can be added to the test sequence file and will be executed during the test run.

• Command line arguments follow the previously introduced JSON syntax definition
• Two or more arguments must be separated by a ‘,‘
• The example above calls the /testcase command line argument with a test case named InsertName as parameter value

Multiple test suites – feature list

This section describes the main features of multiple test suites within Ranorex Studio. It lists what can and can’t be done by means of multiple test suites.

Transferring test suite contents

The contents of one test suite can be transferred (copied, moved) to any other test suite of the same project or another project. This means that test cases, smart folders, setup and teardown regions,  modules, etc. can easily be copied or moved from one test suite to another.

Data integrity

When you copy or move test suite contents to another test suite, data integrity with respect to variables and data binding will remain intact. No data binding is lost.

TestRail integration

TestRail can also export/synchronize multiple test suites per project.

Ranorex Remote

Test sequences can also be run on Ranorex Agents from the remote pad.