NUnit
A guide for generating Trunk-compatible test reports for NUnit
Last updated
A guide for generating Trunk-compatible test reports for NUnit
Last updated
You can automatically detect and manage flaky tests in your NUnit projects by integrating with Trunk. This document explains how to configure NUnit 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 .
Trunk detects flaky tests by analyzing test reports automatically uploaded from your CI jobs. You can do this by generating Trunk-compatible XML reports from your test runs.
You can do this in dotnet with the NUnit's built-in JUnit reporter:
.NET will output each build to the path specified by -o <BUILD_PATH> and test results under a sub-folder of <BUILD PATH>/test-reports, specified by the -- NUnit.TestOutputXml="<XML PATH>" option.
In the example command from the Generating Reports step, the XMLs will be located under ./build/test-reports/junit/*.xml. This is also the glob you'll use to locate the results when uploading test results.
You need to disable automatic retries if you previously included them. Retries compromise the accurate detection of flaky tests.
Omit [Retry(n)] from tests to disable retries.
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:
