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.
   
2. Enter a name for the test suite.
   
3. Click Create.

Result

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: These option are available for test suites.

Note: 
- You can’t move an entire test suite to another project.
- You can move content between test suites (test cases, smart folders, setup/teardown regions, modules, module groups, etc.) by cutting/copying and pasting the items.

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 Run to start the specified test sequence.
    

This section explains where Ranorex stores the sequence and how you can add run parameters.

Test sequence file

When a project contains at least two test suites, Ranorex creates a test sequence configuration file automatically and adds it 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. You can edit this file with any text editor.

Test sequence file content and syntax

The .rxsqc file uses JSON syntax. Each test suite has its own configuration object, and all test suites are listed in an array.

Key syntax basics

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 are reflected in the file in real-time. Inserted command-line arguments remain intact.

Adding command line arguments

You can add command-line arguments to a test suite entry in the .rxsqc file so they are applied 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: When you pass file parameters at runtime, you may need to include file endings (for example, .rxtst). In the .rxsqc file, those file endings are omitted.

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

You can copy or move contents from one test suite to another (within the same project or across projects). This includes test cases, smart folders, setup/teardown regions, modules, module groups, and other test suite items.

Data integrity

Variables and data binding can remain intact when transferring test content, but it depends on what you move.

Warning: Data-binding remains intact if either of the following conditions is true: If data is bound to global parameters that 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.