Dart Test
A guide for generating Trunk-compatible test reports for Dart tests
Last updated
A guide for generating Trunk-compatible test reports for Dart tests
Last updated
You can automatically detect and manage flaky tests in your Dart projects by integrating with Trunk. This document explains how to configure Dart 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 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.
Before you can upload to Trunk, you need to output a Trunk-compatible report. Dart supports JUnit outputs by using the tojunit library. You can install the tojunit library using the following command:
Then, you can convert test reports to a JUnit format by piping it to tojunitand piping the output to a file like this:
The JUnit report is written to the location specified by the tojunit > pipe. In the example above, the test results will be written to ./junit.xml.
You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests.
Dart provides retries through the retry class annotations. Disable retry, use Trunk to detect flaky tests, and use Quarantining to isolate flaky tests dynamically at run time.
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 . 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.
