Ranorex Help Center How can we help you?

XCOPY Deployment

Running tests without Ranorex Installation

Note The way of deploying tests without Ranorex Installation described below is possible but not recommended. Still this approach is documented since it allows to overcome internal policies and/or restrictions inhibiting installations on runtime environments, e.g. due to group policies within domains.

Deploy Ranorex Libraries and Assemblies

The required files for executing Ranorex tests on runtime machines are located in the "bin" folder of the Ranorex installation path. These files can be found easily on machines having a valid Ranorex Installation using the environment variable %RANOREXPATH%. Please copy the whole content of the "bin" folder (including all subdirectories) to a target folder (<TargetFolder>) on the runtime machine.

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

Note It is crucial to deploy the Ranorex Assemblies with exactly the same version that was used to compile the test executable

Deploy Ranorex License Information

In the runtime environment a valid license information needs to be available. Most likely the runtime machine will use a floating license, so the only information necessary can be provided by the license file (Ranorex3_Server.lic). This file can be copied easily from any machine having a floating license installed to the target machine and is located in the path of the environment variable %ALLUSERSPROFILE%. For more information please refer to chapter "Install Ranorex License" in the section "Silent Installation of Ranorex".

Deploy Your Ranorex Test

Ranorex generates the files needed to run automated tests in the "Output Folder" (by default <ProjectPath>\bin\Debug) of a test suite project.
Open output folder from Ranorex Studio

Open output folder from Ranorex Studio

Note You can directly access this folder by right-clicking the current project and choosing "Open Output Folder" in the context menu.

Next to files needed for test execution, additional files are created in the output folder during test execution (e.g. Reports, Screenshots etc.). Those files do not have to be copied. It's recommended to clear your output folder before and then trigger a new build (Build -> "Build Solution" or hot key F8).

Required files for executing Ranorex test automation:

  • Executable file (*.exe)
  • Test Suite File (*.rxtst)

Additionally required on the base of your project needs:

  • Ranorex Module Group (*.rxtmg), only necessary if modules groups are in use
  • Test Data (*.xlsx, *.xlsb, *.xls, *.csv, *), only necessary for data driven tests and if data source files were added to project
  • Module Libraries (*.dll), only necessary if module libraries are linked and embedded functionality is referenced in the Test Suite
  • Sub folder "RepositoryImages" including all files, if exists

Finally copy the files needed to the target machine and place them in the folder where all Ranorex Libraries and Assemblies are already located (<TargetFolder>). Of course, by copying the whole output folder ("bin\debug" by default), you will ensure you have everything possibly required for running your test.

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

Note For executables being explicitly compiled against 64bit CPUs, place these files in the sub folder "x64" of the target folder.