Create an executable build

Create an executable build and include it in Ranorex Studio runtime library, license information, and external files in the build.

An executable build is simply a build of your test that you can execute like a program.

Ranorex Studio automatically creates an executable build of your test whenever you do one of the following:

1. Click RUN to start a test run.

2. Click Build all projects in the solution.

3. Click Build the current project.

When Ranorex Studio builds a test, it automatically copies all the basic required files to the folder binDebug in the respective project’s folder, as shown below. This is called the output folder. You can change the output folder directory in Settings.

1. Default output folder directory for the executable build of a project.

2. The executable of the test is named after the project. In this case, this is Introduction.

3. Configuration files.

4. Module group and test suite files.

5. Required libraries and the settings of the project.

6. Optional external files that were manually included in the output folder.
   In this case, the Ranorex Studio Demo Application is the AUT. Without it, the test would not run correctly. It is small enough to be included in the project. Large AUTs should be preinstalled on the specific runtime environment and not included in the executable build.

 

Note

 

The executable build shown in the above image allows you to run the test on machines that have a full version of Ranorex Studio installed. However, we want to execute tests in runtime environments, for example, machines without a Ranorex Studio installation. This is why we need to include the Ranorex Studio runtime library and licensing information.

 

To execute a test in a runtime environment, you need to include the Ranorex Studio runtime library with the executable build. You do so by activating the option Copy runtime to output in the settings. By default, it is deactivated.

1. In Ranorex Studio, open the Settings.

2. Ensure the General tab is displayed.

3. Check Copy runtime to output and click OK.
   
   

When you create an executable build, Ranorex Studio automatically includes the runtime library under Runtime in the output folder.

To execute a test in a runtime environment, you need to include license information in the executable build.

 

Note

 

Executing a test in a runtime environment requires at least a Ranorex Runtime Floating License.

You can still execute your test if you don’t include license information, but only as part of the Ranorex Studio trial. You cannot execute a test in a runtime environment with the license information of a Node-locked License.

For more information about Ranorex licenses, contact our Sales Team.

 

By default, license information is not included in the executable build. To include it:

1. In Ranorex Studio, open the Settings.

2. Ensure the General tab is displayed.

3. Click Include license information and click OK.

Now when you create an executable build, Ranorex Studio automatically includes the license information file in the executable build.

Sometimes you may want to include external files with your executable build. To do so, you need to first include them in your project and then configure them to be included in builds.

 

Note

 

Examples of external files you may want to include:

• The AUT or required libraries.
• Images or HTML/CSS/XSL files for custom reports.
• Data sources for data-driven tests.
  
  

Now, include the Ranorex Studio Demo Application in the executable build. To do so, first include it in the project:

1. Copy the file to the project folder. In our case, this is the file RxDemoApp.exe.
   
   

2. In the projects view, click the Refresh and the Show all files buttons to display the added file.
   

3. Right-click the file.

4. Click Include in project.

 

Note

 

After including the file, its icon will switch from transparent to fully outlined, and when right-clicking it, the option Exclude from the project will be listed.

 

You’ve included the file in your project. Now, you need to configure it to be included in the output folder when creating an executable build.

5. In the projects view, click the file and press F4 to open the file’s properties.

6. Set Copy to output directory to Always or PreserveNewest.

• • Never: The file won’t be included.
  • Always: The file will be copied each time you create an executable build.
  • PreserveNewest: The file will only be copied if it changed since the last build.