Manual remote execution involves manually running a standalone version of your test on a machine that does not have Ranorex Studio installed and retrieving the report yourself.
Running an executable build through a Ranorex Agent simplifies and automates a large part of this process. For more information, see Ranorex Agents and Agent-Based Remote Execution.
Pack the executable build
You must prepare your test files before moving them to the remote environment. Follow these steps:
- Verify that your test settings allow it to run properly on the remote machine. You are not able to change the deployed test on the remote machine unless you install Ranorex Studio there or use command line arguments, which only offer limited ways of adjusting test execution.
- Ensure you include all required files in your project and that the application includes them in the output directory.
- Create a new Build of your project.
- Navigate to your output folder (for example, bin\Debug) and add all contents to a ZIP archive.
- Transfer the ZIP file to the target machine and extract it.
For more information, see Create an Executable Build.
Run the test
You execute the test either directly on the target machine or through a remote desktop connection.
- Ensure that the unpacked executable build is in the remote machine.
-
Run the test in one of the following ways:
- Navigate to the extracted folder and double-click the [ProjectName].exe file.
-
Open the command line interface and execute the file from there. This allows you to use command line arguments to customize the run.
If you don’t have a license, you can install the free trial license of Ranorex Studio on the remote machine to run the test.
Reporting
When the test completes, the system generates a report just as it does in Ranorex Studio. You find the report files and raw data (1) within the Reports folder of your extracted test directory on the remote machine. You can move these files to your local machine to view them in Ranorex Studio.