> ## 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. # Bazel > A guide for generating Trunk-compatible test reports with Bazel You can automatically [detect and manage flaky tests](../../detection/) in your Bazel projects by integrating with Trunk. This document explains how to configure Bazel to output compatible 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} /> Test uploads locally} /> ## Generating Reports Trunk can parse JSON serialized [Build Event Protocol (BEP) ](https://bazel.build/remote/bep)files to detect flaky tests. You can run tests with Bazel in CI with the `nobuild_event_json_file_path_conversion` option to produce a serialized BEP file: ```sh theme={null} bazel test \ --nobuild_event_json_file_path_conversion ``` ### Report File Path You can specify the path of the generated report through the `build_event_json_file` option: ```sh theme={null} bazel test \ --nobuild_event_json_file_path_conversion --build_event_json_file=build_events.json ``` Trunk can parse the `build_events.json` file to locate your test reports. You will still need to **configure your test runners to output compatible reports**, and you can refer to the guides for [individual test frameworks](./). Trunk accepts BEP files in both JSON and binary formats: * `--build_event_json_file` for JSON * `--build_event_binary_file` for the binary protobuf encoding Pass either file to the analytics CLI's `--bazel-bep-path`. The CLI detects the format automatically, so you don't need to tell it which one you used. ### Build Without the Bytes If your CI environment is set up to [build without the bytes](https://blog.bazel.build/2023/10/06/bwob-in-bazel-7.html), you will need the following flag to pull the reports from the remote execution engine: ```sh theme={null} --remote_download_regex='.*/test.xml' ``` ## Try It Locally ### The Validate Command ```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 --bazel-bep-path=build_events.json ``` ```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 --bazel-bep-path=build_events.json ``` ```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 --bazel-bep-path=build_events.json ``` ```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 --bazel-bep-path=build_events.json ``` ### 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 --bazel-bep-path=build_events.json \ --org-url-slug \ --token ``` ## Next Steps Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below: