NUnit

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.

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.

Generate a compatible test report

Configure the report file path or glob

Disable retries for better detection accuracy

Test uploads locally

Generating Reports

Trunk detects flaky tests by analyzing test results 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:

dotnet test -o build  -- NUnit.TestOutputXml="junit"

Report File Path

.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.

Disable Retries

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.

Try It Locally

The Validate Command

You can validate your test reports using the Trunk Analytics CLI. If you don’t have it installed already, you can install and run the validate command like this:

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 "./build/test-reports/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:

./trunk-analytics-cli upload --junit-paths "./build/test-reports/junit/*.xml" \
    --org-url-slug <TRUNK_ORG_SLUG> \
    --token <TRUNK_ORG_TOKEN>

You can find your Trunk organization slug and token in the settings or by following these instructions. After your upload, you can verify that Trunk has received and processed it successfully in the Uploads tab. Warnings will be displayed if the report has issues.