The Runtime and Remote Execution capability in Ranorex Studio allow you to execute your automated tests outside of your development environment. A runtime environment is a machine without a Ranorex Studio installation that you only use for executing and not building tests. This enables you to distribute tests across multiple physical or virtual machines, and run them in parallel, asynchronously, or based on a schedule.
Basics
The first step in remote test execution is to create an executable build of your test. Then, you deploy this build to a runtime environment, typically a remote machine, and execute it there.
- For information on how to create an executable build and include the Ranorex Studio runtime library, license information, and external files in the build, see Create an Executable Build.
- For information on how to run an executable build through a command line interface and the available command line arguments, see Command Line Execution.
Manual remote testing
In manual remote testing, you pack the executable build and deploy it to the remote machine(s) yourself. You then trigger test execution directly on the remote machine or through a Remote Desktop Protocol (RDP) connection, using the command line.
For more information, see Manual Remote Execution.
Agent-based remote testing
Ranorex Agent is a standalone tool that simplifies and streamlines remote test execution with Ranorex Studio. Agents are installed on remote machines and receive executable builds either through the remote pad in Ranorex Studio or through the command line. Agents automatically execute a test queue and deliver the report to the original machine the test was deployed on.
For more information, see Ranorex Agents and Agent-Based Remote Testing.