> ## Documentation Index > Fetch the complete documentation index at: https://trunk-4cab4936-sam-gutentag-changelog-flaky-tests-no-monito.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # cargo-nextest > A guide for generating Trunk-compatible test reports for Rust You can automatically [detect and manage flaky tests](../../detection/) in your Rust projects by integrating with Trunk. This document explains how to configure cargo-nextest 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 `cargo-nextest` has built-in reporting for JUnit XML reports, which is trunk-compatible. You can enable JUnit reporting by adding the following to your nextest config: ```toml title=".config/nextest.toml" theme={null} [profile.ci.junit] path = "junit.xml" ``` You can invoke this profile when running tests with: ```sh theme={null} cargo nextest run --profile ci ``` ### Report File Path `cargo-nextest` outputs artifacts at `target/nextest` by default. When you provide a profile and a file name via the config example above, it produces a report at `target/nextest/ci/junit.xml`. ### Disable Retries You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests. Omit the `--retries` option. ## Try It Locally ### The Validate Command You can validate your test reports using the [Trunk Analytics CLI](../../reference/cli-reference). If you don't have it installed already, you can install and run the `validate` command like this: ```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 "./target/nextest/ci/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 "./target/nextest/ci/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 "./target/nextest/ci/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 "./target/nextest/ci/junit.xml" ``` This will not upload anything to Trunk. To improve detection accuracy, you should address all errors and warnings before proceeding to the next steps. ### 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 "./target/nextest/ci/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: