Ranorex Studio settings define how the application behaves during test creation and execution. Understanding where these settings are stored and how they behave is essential for managing configurations across different environments and teams.
Machine-stored settings
Machine-stored settings are local to the specific computer where Ranorex Studio is installed and remain constant regardless of which project is open. Review these options by accessing settings from a Ranorex tool without a solution associated with it.
- Open the Ranorex Settings shortcut in your installation directory, usually C:\Program Files (x86)\Ranorex\Studio\Bin.
- Click the Settings icon in the stand-alone Spy dialog.
- Click the Settings icon in the toolbar of the Ranorex Studio start page.
Scope: This category includes both User settings (personal preferences like UI language and themes) and machine-specific configurations.
If you change a machine-stored setting, such as the IDE theme, that change persists even if you close the current solution and open a different one.
Solution-stored settings
Solution-stored settings are specific to an individual test solution and are designed for consistency across a team. Review these options by accessing settings from a Ranorex tool while a solution is open.
To access settings, click SETTINGS…. When a solution is open, the Settings dialog includes the Current recording and Current repository tabs.
These settings are saved in a file named Ranorex.rxsettings located within the Solution Items folder in the Solution Explorer.
Warning: Do not change the name of the settings folder or the Ranorex.rxsettings file. If you open the settings file, it is shown in its raw format. It is not recommended to edit the file in this view
Scope: This category covers Solution settings. These include project-critical configurations such as object recognition (RanoreXPath) rules, plugin behaviors, and default values for the Recorder and Repository.
Because these settings are stored within the project directory, they are shared with other team members via source control (e.g., Git or SVN). This ensures that every person working on the solution uses identical configurations.
If a solution does not contain a settings file, you can add it by clicking the Create solution settings in the Projects view toolbar of a solution.
Behavior during text execution
When a test is executed, either locally or remotely, Ranorex Studio follows a specific priority logic for settings:
-
Solution-stored priority: Ranorex uses
Ranorex.rxsettings, which is copied into the output directory and must be deployed alongside the test executable. -
Machine-stored fallback: If
Ranorex.rxsettingsis missing or is not in the same folder as the executable, Ranorex uses the settings stored locally on the execution machine.
Note: Solution settings are essential for Ranorex Remote and CI/CD pipelines to ensure the execution agent matches the developer's configuration.