[ready to merge] docs(flaky-tests): Setup steps + Validate sections

flaky-tests/get-started/ci-providers/atlassian-bamboo.mdx

@@ -12,16 +12,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -187,6 +187,15 @@ See the [uploader.md](../../reference/cli-reference.md "mention") for all availa
 
 Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step.
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**
 

flaky-tests/get-started/ci-providers/azure-devops-pipelines.mdx

@@ -11,16 +11,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -145,6 +145,15 @@ Ensure you report every test run in CI and **clean up stale files** produced by
 
 [Learn more about cleaning up artifacts in Azure DevOps Pipelines](https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops\&tabs=yaml#clean-the-local-repo-on-the-agent)
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**
 

flaky-tests/get-started/ci-providers/bitbucket-pipelines.mdx

@@ -11,16 +11,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -147,6 +147,15 @@ Ensure you report every test run in CI and **clean up stale files** produced by
 
 You can do this by omitting the `artifacts` definitions in the test steps of your configuration. [Learn more about artifacts in BitBucket Pipelines](https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/).
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**
 

flaky-tests/get-started/ci-providers/buildkite.mdx

@@ -12,16 +12,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -119,6 +119,15 @@ See the [uploader.md](../../reference/cli-reference.md "mention") for all availa
 
 Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step.
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**
 

flaky-tests/get-started/ci-providers/circleci.mdx

@@ -12,16 +12,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -132,6 +132,15 @@ See the [Uploader CLI Reference](../../reference/cli-reference) for all availabl
 
 Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step.
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**
 

flaky-tests/get-started/ci-providers/droneci.mdx

@@ -12,16 +12,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -143,6 +143,15 @@ See the [uploader.md](../../reference/cli-reference.md "mention") for all availa
 
 Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step.
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**
 

flaky-tests/get-started/ci-providers/github-actions.mdx

@@ -6,16 +6,16 @@ Trunk Flaky Tests integrates with your CI by adding a step in your GitHub Action
 
 Before you start these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing Trunk-compatible reports for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as secrets in GitHub Actions
-* [ ] Configure GitHub Actions to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk.
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-your-trunk-token-and-organization-slug-as-secrets">Set your slug and token as secrets in GitHub Actions</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure GitHub Actions to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -224,6 +224,15 @@ You can also wrap the test command with the Trunk Analytics CLI. When wrapping t
 
 Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step.
 
+### Validate Your Uploads
+
+Once your workflow has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check the action logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the repo running the workflow.
+
 ### Getting Direct Links to Job Logs
 
 <Info>

flaky-tests/get-started/ci-providers/gitlab.mdx

@@ -12,16 +12,16 @@ Flaky Test support for source control providers like GitLab and BitBucket is sti
 
 Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework.
 
-### Checklist
+### Setup steps
 
-By the end of this guide, you should achieve the following.
+Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results.
 
-* [ ] Get your Trunk organization slug and token
-* [ ] Set your slug and token as a variable in CI
-* [ ] Configure your CI to upload to Trunk
-* [ ] Validate your uploads in Trunk
-
-After completing these checklist items, you'll be integrated with Trunk. 
+<Steps>
+  <Step title={<a href="#trunk-organization-slug-and-token">Get your Trunk organization slug and token</a>} />
+  <Step title={<a href="#add-the-trunk-token-as-a-secret">Set your slug and token as a variable in CI</a>} />
+  <Step title={<a href="#upload-to-trunk">Configure your CI to upload to Trunk</a>} />
+  <Step title={<a href="#validate-your-uploads">Validate your uploads in Trunk</a>} />
+</Steps>
 
 ### Trunk Organization Slug and Token
 
@@ -135,6 +135,15 @@ See the [uploader.md](../../reference/cli-reference.md "mention") for all availa
 
 Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step.
 
+### Validate Your Uploads
+
+Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results.
+
+- The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on).
+- The **Tests** tab shows individual test cases once an upload has been processed.
+
+If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_TOKEN` and `TRUNK_ORG_SLUG` secrets are set on the project running the pipeline.
+
 <Tip>
 **Have questions?**