While competing in the exacting modern software market, many companies find integrating automated testing into their overall testing process beneficial. This guide will help you better understand the different types of automated test solutions and how developers...
In this chapter, you’ll learn about executing tests in runtime environments, with a focus on remote execution. A runtime environment is a machine without a Ranorex Studio installation that is only used for executing and not building tests. Executing tests on remote machines opens up many possibilities: You can distribute tests on several different physical or virtual machines to run them in parallel, asynchronously, or based on a schedule.
The first step in remote test execution is to create an executable build of your test. You then deploy this build to a runtime environment, typically a remote machine, and execute it there. In ⇢ Create an executable build, you’ll find out how to create an executable build and include the Ranorex Studio runtime library, license information, and external files in the build.
In ⇢ command line execution, you’ll find out how to run an executable build through a command line interface and learn the available command line arguments.
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. This is explained in ⇢ Manual remote testing.
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 from.