The standard report is usually appropriate for most scenarios. However, to suit individual needs, it’s fully customizable. Because customization is a large topic, we’ve split it up into two chapters.
In this chapter, you’ll learn about the basics of customization and go through a few examples to customize the look of the report without coding.
For more complex customizations that involve coding, refer to
Ranorex Studio fundamentals > Reporting > ⇢ Complex customizations.
In this chapter
The explanations in this chapter are based on a sample solution that you can download below.
Theme: Report customization
Time: 15 minutes
Unzip to any folder on your computer.
Start Ranorex Studio and open the solution file
The image below illustrates the process that prepares raw data to be displayed in an easily readable format in the report.
Data from a test run is collected and stored in an XML format. This raw data can also be read and used outside of Ranorex Studio with any XML viewer/editor.
The raw XML data is always saved in the same folder as the corresponding original report file and has the same file name with the added suffix
The raw XML data is used to create a HTML file based on CSS and XSL specifications.
The XSL and CSS specifications used to generate the HTML file are also stored in the same folder as the XML data and the actual report.
To be able to change the layout and content of Ranorex standard reports, a basic understanding of HTML, CSS, XSL, and XML is recommended. Refer to the World Wide Web Consortium (W3C) at www.w3.org for further reading.
The final report generated from XML by XSL and CSS is stored in a HTML-based format in the
Reports folder of the project’s output directory.
Now that we’ve established how reports are generated, we can start customizing the report. There’s a convenient way to do this in Ranorex Studio without affecting the standard report:
In the test suite view, right-click the test suite.
Click the Report tab.
Click Create custom template.
A message appears, telling you where the new report template folder has been created. Confirm with OK.
In the projects view, you can see the new template folder with the copied report files.
CSS, XSL, and image files
You can create as many custom report templates as you want. However, only one template can be active at a time for a test suite.
To create additional custom templates:
Click Reset to default in the Report tab of the test suite properties.
Click Create custom template again and confirm with OK.
Another template folder appears in the projects view.
You can rename custom report templates.
In the projects view, select the template you want to rename.
Press F2 and rename the template folder.
The renamed folder.
This function is used for three different purposes:
Open the Report tab in the test suite properties.
If there’s a custom template currently active, click Reset to default template.
Click Choose custom template….
Choose a custom template in the browser window.
If you want to stop using a custom template, you can reset to the default Ranorex Studio template at any time.
Open the Reports tab in the test suite properties.
Click Reset to default and confirm with OK.
Ranorex Studio has a special mechanism for processing customized report templates, which includes the output folder and the reports folder for each project. Understanding this process is important when you want to include external files in a report template, e.g. a PNG containing your logo, because these files aren’t included in the process by default.
When you execute a test, Ranorex Studio copies all files needed for the test run into a designated output folder called
binDebug, which is located in your project’s folder. This includes the standard files created as part of a custom report template, but excludes external files, such as a logo. External files are copied to the output folder only if they are configured to be and therefore won’t appear in your report by default. How to do this is explained in the next section.
Copy of the customized report template folder (FrogConsulting in this example) in the output folder
Reports folder in the output folder
Report file (.rxlog) and corresponding raw data file (.rxlog.data)
CSS and XSL specification files and default logo file RanorexReport.png
The image and descriptions below illustrate the process. As mentioned earlier, external files need special configuration to be included in the process. In this case, we assume that this has been done. You can learn how to do so further below.
A custom report template has been applied to the test suite. The folder for the custom template is located in your project’s folder, FrogConsulting in this example.
On the first test run, the custom template folder is copied directly to the output folder of the project.
The report layout files (CSS, XSL, and custom files) are also copied from the template folder directly to the Reports folder in the output folder of the project.
On subsequent runs, the custom template folders in the project folder and the output folder are synchronized, i.e. the output folder always contains the newest files from the custom template folder.
By default, Ranorex Studio includes internal files (.rxlog, rxlog.data, .css, .xsl, .png, images, videos) in the reporting process, i.e. only these are copied to the output folder. For external files such as logos to show up in your custom report, you will need to include them in this process manually.
Copy the external file(s) to the folder of the custom report template you want them to be part of.
In the projects view in Ranorex Studio, click the refresh button to see the file in the template’s folder.
Right-click the external file.
Click Include in project.
The file is now included in the project, but we’re not finished yet.
Any file(s) copied into the custom report folder are initially not part of the project, meaning they aren’t included in the reporting process either. They appear grayed out in the projects view.
Select the external file and press F4 to open its properties.
You can see Copy to output folder is set to Never, so the file would be excluded from the reporting process. Change it to Always or Preserve newest.
Never is the default setting for any newly included external files.
Always means the file will be copied to the output folder for each test run.
Preserve newest means the file will only be copied if the version in the
Reports folder is newer than the already existing one in the output folder. If no file exists yet in the output folder, it will always be copied.
In this example, you’ll change the background color of the report and replace the Ranorex logo with a custom one. The example is based on the sample solution that’s available for download at the beginning of this chapter.
We’ve prepared a sample logo. The green background has the HEX value
The sample logo is already in the FrogConsulting custom report template folder.
To replace the logo, you’ll need to make changes to the CSS specification file.
In the projects view, double-click the CSS specification file.
It opens in a new tab.
Go to the end of the file and find the customization area.
Delete this line to uncomment the customization section and then replace its contents as described below.
Report info box alignment
Finally, a top margin of 40px is set for the general information box.
There are also various options for changing the contents of the report. We’ll go through three examples that will introduce the basic principle and help you customize reports according to your own ideas. In the first example, you’ll customize the report so that the entry for “Computer/Endpoint” reads “Username” and instead of the machine name displays the username.
The line in the XSL file that defines the title of the entry.
The “host” line in the raw data file. It contains the actual computer/endpoint name.
This line in the XSL file gets the computer/endpoint name from the “host” line in the raw data file and displays it below the “Computer/Endpoint” entry in the report.
To replace the “Computer/Endpoint” entry with “Username” and display the username:
In the XSL specification, replace “Computer/Endpoint” with “Frog user”.
Also in the XSL specification, replace the variable
Save and close the file.
In this example, you’ll change the formatting of a specific type of report message.
As you can see in the image below, messages in the default report with the Success level are printed in green font. Let’s change this to a bold blue font.
Default Success message in green
Open the CSS specification file.
Find the color definition for Success messages and copy it.
Paste it in the customization section at the end of the CSS file and modify it as shown in the image.
Save and close the file.
Default font color definition for Success messages
New definition in the customization section. Overrides the default definition.
In this example, you’ll remove information from the report. This is useful when something’s not relevant and you want to free up space in the report.
In our example, we want to remove the Time column for report messages.
Open the XSL specification file.
Find all instances of Time in the file.
These are the lines that define the Time column in the XSL file.
Deactivate all of them by commenting them out as shown below.
This code gets the time values for each action line and displays them in the correct place.
Deactivate it by commenting it out as below.