cargo-nextest
A guide for generating Trunk-compatible test reports for Rust
Last updated
A guide for generating Trunk-compatible test reports for Rust
Last updated
You can automatically 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.
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 .
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:
You can invoke this profile when running tests with:
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.
You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests.
Omit the --retries option.
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:
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:
