GoogleTest
A guide for generating Trunk-compatible test reports for GoogleTest
Last updated
A guide for generating Trunk-compatible test reports for GoogleTest
Last updated
You can automatically in your GoogleTest projects by integrating with Trunk. This document explains how to configure GoogleTest to output JUnit XML reports that can be uploaded to Trunk for analysis.
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 .
Before you can integrate with Trunk, you need to generate a Trunk-compatible report. For GoogleTest, the built in XML reporter will work. You can use the argument when you run your built test project:
By default, the JUnit report will be written to a test_detail.xml
file.
You can specify a custom directory and filename with:
For example, the following argument writes a JUnit report to ./junit.xml
:
You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests.
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:
Omit the argument if you've previously configured your CI with these options to disable retries.
You can validate your test reports using the . 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.