Create an executable build
On this page, you’ll find out how to create an executable build, and how to include the 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.
Create an executable build
Ranorex Studio automatically creates an executable build of your test whenever you do one of the following:
Click Build all projects in the solution.
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 the >Settings.
Executable of the test, named after the project. In our case, this is Introduction.
Configuration files.
Module group and test suite files.
Required libraries and the settings of the project.
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 with the project. Large AUTs should be preinstalled on the specific runtime environment and not included in the executable build.
Note
Include Ranorex Studio runtime library
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.
In Ranorex Studio, open the settings.
Ensure the General tab is displayed.
Check Copy runtime to output and click OK.
Include license information
To execute a test in a runtime environment, you need to include license information in the executable build.
Note
For more information about Ranorex licenses, contact our Sales Team.
In Ranorex Studio, open the settings.
Ensure the General tab is displayed.
Click Include license information and click OK.
Include external files
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
- The AUT or required libraries.
- Images or HTML/CSS/XSL files for custom reports.
- Data sources for data-driven tests.
Copy the file to the project folder. In our case, this is the file RxDemoApp.exe.
Click Include in project.
Note
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.
In the projects view, click the file and press F4 to open the file’s properties.
Set Copy to output directory to Always or PreserveNewest.
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.