Manage multiple test suites

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

1. In the Studio toolbar, click the Add test suite button.

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

3. Name the test suite.

4. Click Create.

Result(s)

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

1. The initial test suite in the projects view.

2. The newly added test suite in the projects view.

3. 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.

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:

1. Cut, Copy, Paste: An entire test suite cannot be cut, copied, or pasted. Similarly, you cannot move an entire test suite to another project.

2. Delete, Rename: Test suites can be deleted and renamed.

Note: 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.

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.

1. Startup project selection: If you have multiple projects with multiple test suites.

2. Select the project to configure here. By default, the current test project is pre-selected.

3. Use the order buttons on the left to change the position of the test suites in the test sequence.
   

4. Use the ON/OFF buttons to exclude selected test suites from the test run.

5. Click the Run button to start the specified test sequence.

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.

1. Test sequence file in the project view

2. Test sequence file in the project folder

Note: The test sequence file has the file ending .rxsqc and can be edited with any text editor.

Test sequence file content and syntax

1. To open the test sequence file, double-click it.

2. It appears in its tab.
   

1. Text content of the test sequence file:

• [ ] 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 ,

Note: 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.

1. Example command line argument /testcase

• 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

Hint: While command line arguments in the runtime environment require file endings (for example, .rxtst) for file parameters, these endings are discarded in the test sequence file.

This section describes the main features of multiple test suites within Ranorex Studio. It lists what can and can’t be done using 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 for variables and data binding will remain intact. No data binding is lost.

Warning: Data-binding will remain intact if either of the following conditions is true: 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 that are not copied, data binding is lost!

TestRail integration

TestRail can also export/synchronize multiple test suites per project. The TestRail integration with Ranorex is described in TestRail integration.

Ranorex Remote

Test sequences can also be run on Ranorex Agents from the remote pad, for more information, review the article Overview.