Run Configurations Basics

Run configurations let you save different selections of test containers (test cases, smart folders, module groups, etc.) for the same test suite, so you can run “Smoke,” “Regression,” or “Login-only” without manually checking/unchecking items every time. They’re especially useful when you regularly run the same test suite with different parts enabled.

When to use run configurations

Use run configurations when you want to:

• Run only a subset of a large test suite (for example, a smoke run).
• Run different test sets on different schedules (daily smoke vs weekly full run).
• Ensure CI runs are repeatable, even when the test suite grows over time.
• Avoid “blocked” test cases caused by intentionally deselecting containers.

Tip: If you have deselected test containers but only one saved configuration (often the default), create named run configurations so your intent is clear and repeatable.

How run configurations affect results and reports

• The report reflects the structure and containers that were executed.

Deselected containers can show up as blocked (depending on what was part of the run and how the run was aborted/filtered).

In reporting/CI, you can also include the run configuration name in the report filenames (as a placeholder %R).

Create and use run configurations in Ranorex Studio

In the test suite view, you can:

1. Select or create a run configuration using the Test Suite view. You can:
2. Select or create a run configuration from the run configurations drop-down (Manage run configurations…).
3. Check/uncheck the test cases and smart folders you want to include.

4. Save the configuration with a clear name (for example: Smoke, Regression, LoginOnly).

   Naming tip: If you reference a run configuration from CI, enter the name exactly (same spelling/case) as in Ranorex.

Use run configurations outside Studio

Command line

Run an executable build in a specific run configuration using:

<YourTest>.exe /rc:<run configuration>

Example:

RxDatabase.exe /rc:Smoke

If you have multiple test suites, specify the test suite file as well:

RxDatabase.exe /ts:MySuite.rxtst /rc:Smoke

Note: If you don’t pass arguments, the executable runs using the configuration that was active when the build was created.

Jenkins

In the Run a Ranorex test suite build step, you can enter a run configuration.
If you don’t, Jenkins uses the run configuration that was active when the solution was last saved.
The name must match exactly.

Azure DevOps pipelines

The ADO task includes a field for the run configuration. Enter it exactly as named in Ranorex Studio.

Agent-based remote execution

Agents allow selecting a test suite and specifying a run configuration (with some limitations when executing test sequences).