Gradle
A guide for generating Trunk-compatible test reports for Gradle
Last updated
A guide for generating Trunk-compatible test reports for Gradle
Last updated
You can automatically detect and manage flaky tests in your Gradle projects by integrating with Trunk. This document explains how to configure Gradle to output JUnit XML reports that can be uploaded to Trunk for analysis.
Tests run with Gradle will generate JUnit XML reports by default and are compatible with Trunk. You can further configure reporting behavior in your build.gradle.kts or build.gradle.
By default, Android projects will produce a directory with JUnit XML reports under ./app/build/test-results/test. You can locate these files with the glob "./app/build/test-results/test/*.xml".
If you wish to override the default test result path, you can do so in the build.gradle.kts or build.gradle files:
This example will write report files to "./app/build/junit-reports/test/*.xml"
You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests. You should disable retries for accurate detection and use the Quarantining feature to stop flaky tests from failing your CI jobs.
If you've enabled retries using a plugin like the test-retry-gradle-plugin, disable it when running tests for Trunk flaky tests.
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.
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:
By the end of this guide, you should achieve the following before proceeding to the next steps 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 configure uploads in CI.
