> ## Documentation Index > Fetch the complete documentation index at: https://docs.trunk.io/llms.txt > Use this file to discover all available pages before exploring further. # Kotest > A guide for generating Trunk-compatible test reports for Kotest You can automatically [detect and manage flaky tests](../../detection/) in your Kotest projects by integrating with Trunk. This document explains how to configure Kotest 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 Steps for generating JUnit XML reports for Kotest depend on the build system you use for your project: Tests run with Gradle will generate Trunk-compatible JUnit XML reports by default. You can further [configure reporting behavior](https://docs.gradle.org/8.10.2/userguide/java_testing.html#test_reporting) in your `build.gradle.kts` or `build.gradle`. Kotest projects using Maven require the following to be added to a project's `pom.xml` so JUnit XML reports can be generated: * the `maven-surefire-plugin` must be added to the `plugins` section of `pom.xml` ```xml title="pom.xml" theme={null} org.apache.maven.plugins maven-surefire-plugin 3.2.2 ``` * the `kotest-extensions-junitxml` must be added to the `dependencies` section of `pom.xml` ```xml title="pom.xml" theme={null} io.kotest kotest-extensions-junitxml-jvm 5.9.0 test ``` ### Report File Path You can configure the path for generated JUnit XML files: By default, Kotlin projects will produce a directory with JUnit XML reports under `./app/build/test-results/test`. You can locate these files with the glob `"./app/build/test-results/test/*.xml"`. If you wish to override the default test result path, you can do so in the `build.gradle.kts` or `build.gradle` files: ```kotlin title="build.gradle.kts (Kotlin) or build.gradle (Groovy)" theme={null} java.testResultsDir = layout.buildDirectory.dir("junit-reports") ``` You can change the report file path by configuring the `reportsDirectory` in your `maven-surefire-plugin` in your `pom.xml` file: ```xml title="pom.xml" theme={null} org.apache.maven.plugins maven-surefire-plugin 3.2.2 ${project.build.directory}/junit/ ``` The example above will output JUnit XML reports that can be located with the `/target/junit/*.xml` glob. ### Disable Retries You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests. You should disable retries for accurate detection and use the [Quarantining](../../quarantining/) feature to stop flaky tests from failing your CI jobs. If you've enabled retries using a plugin like the [test-retry-gradle-plugin](https://github.com/gradle/test-retry-gradle-plugin), disable it when running tests for Trunk Flaky Tests. Maven uses the `maven-surefire-plugin` to run tests, which allows you to control the test retry behavior. You can disable retries by specifying 0 retries: ``` mvn -Dsurefire.rerunFailingTestsCount=0 test ``` ## 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: The `validate` and `upload` examples below use the **Gradle default** output path. Point `--junit-paths` at the glob that matches your build: * **Gradle** (default): `./app/build/test-results/test/*.xml` * **Gradle** with the `testResultsDir` override shown above: `./app/build/junit-reports/test/*.xml` * **Maven**: `./target/junit/*.xml` ```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 "./app/build/test-results/test/*.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 "./app/build/test-results/test/*.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 "./app/build/test-results/test/*.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 "./app/build/test-results/test/*.xml" ``` Make sure to specify the path to your JUnit XML test reports. **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 "./app/build/test-results/test/*.xml" \ --org-url-slug \ --token ``` You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). 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.

## Next Steps Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below: