> ## Documentation Index > Fetch the complete documentation index at: https://trunk-4cab4936-mintlify-9f2501e3.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Dart Test > A guide for generating Trunk-compatible test reports for Dart tests You can automatically [detect and manage flaky tests](../../detection/) 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. ## Setup steps Work through the steps below in order. Once you've finished the last one, you'll be ready to move on to [configure uploads in CI](../ci-providers/). Generate a compatible test report} /> Configure the report file path or glob} /> Disable retries for better detection accuracy} /> Test uploads locally} /> ## Generating Reports 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: ```sh theme={null} dart pub global activate junitreport ``` Then, you can convert test reports to a JUnit format by piping it to `tojunit`and piping the output to a file like this: ```sh theme={null} dart test --reporter json | tojunit > junit.xml ``` ### Report File Path 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`. ### Disable Retries 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](https://pub.dev/documentation/test/latest/test/Retry-class.html). Disable retry, use Trunk to [detect](../../detection/)[ flaky tests](../../detection/), and use Quarantining to isolate flaky tests dynamically at run time. ## Try It Locally ### The Validate Command ```bash Linux (x64) theme={null} SKU="trunk-analytics-cli-x86_64-unknown-linux.tar.gz" curl -fL --retry 3 \ "https://github.com/trunk-io/analytics-cli/releases/latest/download/${SKU}" \ | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli validate --junit-paths "./junit.xml" ``` ```bash Linux (arm64) theme={null} SKU="trunk-analytics-cli-aarch64-unknown-linux.tar.gz" curl -fL --retry 3 \ "https://github.com/trunk-io/analytics-cli/releases/latest/download/${SKU}" \ | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli validate --junit-paths "./junit.xml" ``` ```bash macOS (arm64) theme={null} SKU="trunk-analytics-cli-aarch64-apple-darwin.tar.gz" curl -fL --retry 3 \ "https://github.com/trunk-io/analytics-cli/releases/latest/download/${SKU}" \ | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli validate --junit-paths "./junit.xml" ``` ```bash macOS (x64) theme={null} SKU="trunk-analytics-cli-x86_64-apple-darwin.tar.gz" curl -fL --retry 3 \ "https://github.com/trunk-io/analytics-cli/releases/latest/download/${SKU}" \ | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli validate --junit-paths "./junit.xml" ``` ### Test Upload 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: ```sh theme={null} ./trunk-analytics-cli upload --junit-paths "./junit.xml" \ --org-url-slug \ --token ``` ## Next Steps Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below: