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.
In this chapter
Create a new test suite
To add a test suite to an existing project, follow the instructions below:
Adding a new test suite
In the Studio toolbar, click the Add test suite button.
In the dialog that appears, verify that Test suite is selected as the template.
Name the test suite.
The new test suite appears in the project view. Usually, it also opens automatically in the test suite view.
Newly added test suite
The initial test suite in the projects view.
The newly added test suite in the projects view.
The test suite tabs below the Ranorex Studio toolbar.
The new test suite file also appears in the Ranorex Studio Projects folder of your test solution.
Test suite files in the Ranorex Studio Projects folder
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:
Test suite context menu
Cut, Copy, Paste
- An entire test suite cannot be cut, copied, or pasted.
- Similarly, you can’t move an entire test suite to another project.
- Test suites can be deleted.
- Test suites can be renamed.
While you can’t move an entire test suite, you can move test suite content between test suites. Simply cut/copy and paste the desired test cases, smart folders, modules, etc.
Set the test sequence
Once a project contains at least two test suites, you can specify a sequence for the test suites.
If your project contains at least two test suites, a context menu will be added to the RUN button. Click it to open the test sequence configuration dialog.
Multiple test suites – test sequence configuration
Startup project selection
- 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.
A deselected test suite
Select the run configuration for each test suite.
Click the Run button to start the specified test sequence.
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 storage location
Test sequence file in the project view
Test sequence file in the project folder
The test sequence file has the file ending
.rxsqc and can be edited with any text editor.
Test sequence file content and syntax
Test sequence file content
To open the test sequence file, double-click it. It appears in its own tab.
]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
You can configure your test sequence in the configuration dialog while the test sequence file is open. The changes will be reflected in the file in real time. Inserted command line arguments will remain intact.
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 in test sequence file
Example command line argument
- Command line arguments follow the previously introduced JSON syntax definition
- Two or more arguments must be separated by a ‘
- The example above calls the
/testcasecommand line argument with a test case named
InsertNameas parameter value
Command line arguments for test suites are explained in Ranorex Studio fundamentals > Test suite > ⇢ Run tests without Ranorex Studio.
While command line arguments in the runtime environment require file endings (i.e.
.rxtst) for file parameters, these endings are discarded in the test sequence file.
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.
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.
Data-binding will remain intact if either of the following conditions is true:
- data is bound to global parameters which are also available in the destination test suite
- the complete data environment is copied.
If data is bound to parent test cases or parent smart folders which are not copied, data binding will be lost!
TestRail can also export/synchronize multiple test suites per project.
Test sequences can also be run on Ranorex Agents from the remote pad.