XCOPY Deployment

XCOPY deployment lets you run Ranorex tests on a runtime machine without installing Ranorex Studio by copying the required Ranorex runtime files, license information, and your test output to the target machine.

Important: This deployment method is possible but not recommended. It is mainly intended for environments where internal policies restrict software installation (for example, domain group policies on runtime machines).

Deploy Ranorex libraries and assemblies

The files required to execute Ranorex tests are located in the bin folder of the Ranorex installation directory.

On a machine with Ranorex installed, you can locate these files using the environment variable %RANOREXPATH%.

1. On a machine with Ranorex installed, open File Explorer.
2. Navigate to:
   "%RANOREXPATH%\bin"
3. Copy the entire contents of the bin folder (including all subfolders) to a target folder on the runtime machine (for example, <TargetFolder>).

Example (copy via portable media):

• xcopy "%RANOREXPATH%\bin\*.*" <PortableMedia>\xcopy
• xcopy <PortableMedia> <TargetFolder>

Important: Always deploy Ranorex assemblies from the same version of Ranorex that was used to compile the test executable.

Deploy Ranorex license information

A runtime machine must have access to valid license information.

In most XCOPY deployment scenarios, the runtime machine uses a floating license and Subscription licensing (online and self-hosted). In that case, the required information is provided by the license file:

• Ranorex3.Server.lic

This file can be copied from any machine where the floating license is installed. It is located under the path defined by the environment variable %ALLUSERSPROFILE%.

1. On a machine with the floating license installed, locate Ranorex3.Server.lic under %ALLUSERSPROFILE%.
2. Copy the file to the runtime machine (same path structure is recommended).

For details, see Install Ranorex License in Silent Installation of Ranorex.

Deploy your Ranorex test

Ranorex creates the files required to run automated tests in the Output Folder of your test suite project (by default):
<ProjectPath>\bin\Debug

Open the Output Folder

You can open the output folder directly in Ranorex Studio:

1. In the Projects view, right-click the current project.
2. Click Open Output Folder.
   

Tip: You can always access this folder by right-clicking the project and selecting Open Output Folder from the context menu.

What to copy (and what not to copy)

During execution, Ranorex may create additional output files (for example, reports and screenshots). These files are created at runtime and do not need to be copied as part of deployment.

To avoid deploying outdated artifacts, it’s recommended to clear the output folder before generating a new build:

• Build > Build Solution, or press F8.

Required files

• Executable file (*.exe)
• Test suite file (*.rxtst)

Optional files (based on your project needs)

• Ranorex module group (*.rxtmg) — required only if module groups are used
• Test data (*.xlsx, *.xlsb, *.xls, *.csv, *) — required for data-driven tests when data sources are part of the project
• Module libraries (*.dll) — required if your test references linked module libraries
• Sub folder RepositoryImages, including all files (if exists)

Copy the test files to the runtime machine

After collecting the required files:

1. Copy them to the runtime machine.
2. Place them in the same folder where you deployed the Ranorex assemblies (<TargetFolder>).

If you copy the entire output folder (by default bin\Debug) You ensure you include everything needed to run the test.

Example

• xcopy "<RanorexProject>\bin\debug\*.*" <PortableMedia>\xcopy
• xcopy <PortableMedia> <TargetFolder>

Note: If your executable was explicitly compiled for 64-bit, place the files in the x64 subfolder of the target folder.