New test analytics doc for docs.sentry (#14296)

## DESCRIBE YOUR PR
Sentry Prevent is adding in Test Analytics to our product. 

- Rename `sentry-prevent-ai`:
https://sentry-docs-git-sentry-prevent-test-analytics-docs.sentry.dev/product/ai-in-sentry/ai-code-review/
(should redirect when on
https://sentry-docs-git-sentry-prevent-test-analytics-docs.sentry.dev/product/ai-in-sentry/sentry-prevent-ai/
)
- Test analytics page:
https://sentry-docs-git-sentry-prevent-test-analytics-docs.sentry.dev/product/test-analytics/
- CLI:
https://sentry-docs-git-sentry-prevent-test-analytics-docs.sentry.dev/product/test-analytics/sentry-prevent-cli/

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [x] Other deadline: Sept 23
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [x] Checked Vercel preview for correctness, including links
- [x] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [x] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

---------

Co-authored-by: Shannon Anahata <[email protected]>
Co-authored-by: Alex Krawiec <[email protected]>

Author: 3 people

docs/product/test-analytics/img/TA-comment.png

@@ -0,0 +1,103 @@
+---
+title: Test Analytics
+sidebar_order: 135
+description: Learn how Sentry's Test Analytics tools can help you improve your code.
+---
+
+Sentry Test Analytics provides actionable insights into your CI test runs, helping you identify flaky tests, track failures, and optimize your test suite for faster, more reliable deployments. 
+
+## Why Use Test Analytics?
+
+- **Spot Flaky Tests:** Quickly identify and address tests that fail intermittently, reducing noise and wasted debugging time
+- **Track Failures and Trends:** Monitor cumulative failures, slowest tests, and overall test run efficiency to improve CI reliability
+- **Get Actionable Insights:** See which lines of code failed within tests, and prioritize fixes
+- **Leverage Sentry Integration:** Access test analytics alongside your error and performance data for a unified developer experience
+
+## Getting Started
+
+<Alert>
+  Sentry Test Analytics is currently in <strong>beta</strong>. Beta features are still a work in progress and may have bugs. 
+</Alert>
+
+![Test Analytics Dashboard](./img/TA-dash.png)
+
+To use Sentry Test Analytics, you’ll need to install the [Sentry app](https://github.com/apps/sentry-io) on your GitHub organization or specific repositories. Once installed, choose your JUnit XML Report framework and [set your permissions](#permissions-and-repository-tokens) using a repository secret.
+
+<Alert>
+**The only test result file format we support is JUnit XML**. Most test frameworks support outputting test results in this format, with some configuration.
+
+Each testing framework will have slight differences in the JUnit XML format it outputs, but we aim to support all of them.
+</Alert>
+
+**There are two ways to upload your test results:**
+
+### 1. Use GitHub Actions to Run Your CI
+If you are already using GitHub Actions, you can use the `getsentry/prevent-action` script to upload your test results.
+
+```yaml
+- name: Upload test results to Sentry
+  if: ${{ !cancelled() }}
+  uses: getsentry/prevent-action
+  with:
+    token: ${{ secrets.SENTRY_PREVENT_TOKEN }}
+```
+
+You can also use [Open ID Connect](https://docs.github.com/en/actions/concepts/security/openid-connect) instead of the prevent tokens a way to authenticate your GitHub Actions workflow.
+
+### 2. Use [Sentry Prevent CLI](/product/test-analytics/sentry-prevent-cli/) to Upload Testing Reports
+If you do not use Github Actions, install the Sentry Prevent CLI using `pip install sentry-prevent-cli` (for Python), or use a binary platform.
+
+```bash {tabTitle:macos}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-macos -o sentry-prevent-cli
+chmod +x sentry-prevent-cli
+```
+
+```bash {tabTitle:linux}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-linux -o sentry-prevent-cli
+chmod +x sentry-prevent-cli
+```
+
+```bash {tabTitle:alpine linux}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-alpine -o sentry-prevent-cli
+chmod +x sentry-prevent-cli
+```
+
+```bash {tabTitle:windows}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-windows.exe -o sentry-prevent-cli.exe
+```
+
+```bash {tabTitle:linux arm64}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-linux-arm64 -o sentry-prevent-cli
+chmod +x sentry-prevent-cli
+```
+
+```bash {tabTitle:alpine linux arm64}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-alpine-arm64 -o sentry-prevent-cli
+chmod +x sentry-prevent-cli
+```
+
+Then, upload your test results using the CLI:
+
+```bash
+sentry-prevent-cli upload --report-type test-results --token <PREVENT_TOKEN>
+```
+
+### Run Your Test Suite
+Now that you've configured your CI to upload your test results, you can inspect the workflow logs to see if the call to Sentry succeeded. You need to have some failed tests to view the failed tests report. 
+
+## Viewing Test Analytics
+
+After your workflow runs, view failed tests in the [failed tests dashboard](https://sentry.io/prevent/tests/?filterBy=failedTests), or in your GitHub pull request comments.
+
+![Test Analytics comment](./img/TA-comment.png)
+
+You can see a complete overview of your test analytics in the [test analytics dashboard](https://sentry.io/prevent/tests/).
+
+##  Permissions and Repository Tokens
+When configuring Test Analytics, you'll be asked to choose your upload permissions. For GitHub Actions, you can use [OpenID Connect](https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect), or generate a repository token. Using the CLI, generate a repository token. 
+
+You can find a list of repository tokens on the Sentry Prevent [tokens page](https://sentry.io/prevent/tokens/).
+
+## Read Next
+
+<PageGrid />

docs/product/test-analytics/img/TA-dash.png

@@ -0,0 +1,72 @@
+---
+title: Sentry Prevent CLI
+sidebar_order: 10
+description: Learn how to use the Sentry Prevent CLI to upload test results to Sentry.
+---
+
+## Installation
+
+<Alert>
+  While the snippets below can be used to download and use the CLI directly, it is highly recommended to perform signature and SHASUM verification to ensure integrity of the CLI before use. See [Integrity Checking the Uploader](/product/test-analytics/sentry-prevent-cli/#integrity-checking-the-cli) below for more information.
+</Alert>
+
+For `Python`, install the Sentry Prevent CLI using `pip install sentry-prevent-cli`. You need to have `Python3` as the default.
+
+```bash
+pip install sentry-prevent-cli
+```
+
+For `binary platforms`, use the following commands to download the latest version of the Sentry Prevent CLI.
+
+```bash {tabTitle:macos}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-macos -o sentry-prevent-cli_macos
+chmod +x sentry-prevent-cli_macos
+```
+
+```bash {tabTitle:linux x64_64}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-linux -o sentry-prevent-cli_linux_x64_64
+chmod +x sentry-prevent-cli_linux_x64_64
+```
+
+```bash {tabTitle:linux arm64}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-linux-arm64 -o sentry-prevent-cli_linux_arm64
+chmod +x sentry-prevent-cli_linux_arm64
+```
+
+```bash {tabTitle:alpine linux x64_64}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-alpine -o sentry-prevent-cli_alpine_x64_64
+chmod +x sentry-prevent-cli_alpine_x64_64
+```
+
+```bash {tabTitle:alpine linux arm64}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-alpine-arm64 -o sentry-prevent-cli_alpine_arm64
+chmod +x sentry-prevent-cli_alpine_arm64
+```
+
+```bash {tabTitle:windows}
+curl -L https://github.com/getsentry/sentry-prevent-cli/releases/latest/download/sentry-prevent-cli-windows.exe -o sentry-prevent-cli_windows.exe
+```
+## Uploading Test Results
+
+To upload test results, use the following command:
+
+```bash
+sentry-prevent-cli upload --report-type test-results --token <PREVENT_TOKEN>
+```
+
+## Integrity Checking the CLI
+
+GitHub releases also includes the SHA for each asset. You can run
+
+```bash
+shasum -a 256 <filename>
+```
+
+or
+
+```bash
+sha256sum <filename>
+```
+
+and compare the checksum generated with that from GitHub releases.
+