Robot Framework
A guide for generating Trunk-compatible test reports for Robot Framework
Last updated
A guide for generating Trunk-compatible test reports for Robot Framework
Last updated
You can automatically detect and manage flaky tests in your projects running tests with Robot by integrating with Trunk. This document explains how to configure Robot to output JUnit XML reports that can be uploaded to Trunk for analysis.
Trunk detects flaky tests by analyzing test reports automatically uploaded from your CI jobs. You can do this by generating Trunk-compatible XML reports from your test runs.
To output compatible repports, add the --xunit argument to your robot command:
The JUnit report will be written to the location specified by the --xunit argument. In the example above, it would be at ./junit.xml.
You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests. You should disable them and prefer using the Quarantine feature to mitigate the negative impact of Flaky Tests.
Omit the --rerunfailed flag and remove any RetryFailed Listeners previously configured to run as part of your CI pipeline to disable retries.
Before modifying your CI jobs to automatically upload test results to Trunk, try uploading a single test run manually.
You make an upload to Trunk using the following command:
Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below:
You can validate your test reports using the Trunk CLI. If you don't have it installed already, you can install and run the validate command like this:
This will not upload anything to Trunk. To improve detection accuracy, you should address all errors and warnings before proceeding to the next steps.
By the end of this guide, you should achieve the following before proceeding to the to configure your CI provider.
After correctly generating reports following the above steps, you'll be ready to move on to the next steps to .
