You can add multiple test suites per project and run them in sequence. This is especially useful when collaborating with others.
In this chapter
Creating a new test suite
Creating (i.e. adding) a new test suite is easy. Follow the instructions below to see how it works.
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
Give the test suite a name.
The new test suite appears in the projects view. Usually, it is also automatically opened 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 Studio toolbar.
Additionally, you can find the test suite file 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
Test suites behave in a special way when it comes to cutting, copying, pasting, deleting, and moving them. If you select a test suite in the projects view and open the context menu, it’ll be displayed like this:
Test suite context menu
Cut, Copy, Paste
- Test suites itself cannot be cut, copied, or pasted.
- In other words, you can’t move test suites to other projects.
- Test suites can be deleted.
- Test suites can be renamed.
While you can’t move test suites themselves, you can move their content to other test suites. Simply cut/copy and paste the desired test cases, smart folders, modules, etc.
Once a project contains at least two test suites, you can specify a test sequence for the test suites.
Multiple test suites – test sequence configuration
Startup project selection
- If you have multiple projects with multiple test suites, you can select which project you want to configure the test sequence for here.
- By default, the current test project is pre-selected.
The order buttons on the left allow you to change the position of the test suites in the test sequence. The ON/OFF buttons allow you to exclude selected test suites from the test run.
A deselected test suite
Finally, the Run button starts the specified test sequence.
Test sequence file & parameters
This section introduces the configuration file where the test sequence is stored and how to add test suite run parameters to this file.
Test sequence file
Whenever a project contains at least two test suites, a test sequence file with all configuration information is created and added to the project folder.
Test sequence file storage location
Test sequence file in the projects view
Test sequence file in the
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
]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
- 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 introduced and explained in Ranorex Studio fundamentals > Test suite > ⇢ Running tests without Ranorex Studio.
Whereas 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.
Transfering test suite contents
The contents of one test suite can be
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 either
- if data is bound to global parameters which are also available in the destination test suite
- or 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.