diff --git a/src/content/docs/test-insights/test-frameworks/_review-in-test-insights.mdx b/src/content/docs/test-insights/test-frameworks/_review-in-test-insights.mdx
new file mode 100644
index 0000000000..b8e4dd3a88
--- /dev/null
+++ b/src/content/docs/test-insights/test-frameworks/_review-in-test-insights.mdx
@@ -0,0 +1,3 @@
+You can then review your test results, including any failures or flaky tests,
+directly in the [Test Insights
+dashboard](https://dashboard.mergify.com/test-insights/detection).
diff --git a/src/content/docs/test-insights/test-frameworks/cypress.mdx b/src/content/docs/test-insights/test-frameworks/cypress.mdx
index 26421b3d9f..cd6cb38b91 100644
--- a/src/content/docs/test-insights/test-frameworks/cypress.mdx
+++ b/src/content/docs/test-insights/test-frameworks/cypress.mdx
@@ -14,6 +14,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={cypressLogo} alt="Cypress logo" />
 
@@ -81,8 +82,7 @@ After pushing these changes:
 2. Cypress generates JUnit files.
 3. The Mergify CI action uploads that file to Test Insights.
 
-You can then see your test results, including failures and flaky tests,
-directly in the Test Insights dashboard.
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/golang.mdx b/src/content/docs/test-insights/test-frameworks/golang.mdx
index 512bb049d5..f42674081d 100644
--- a/src/content/docs/test-insights/test-frameworks/golang.mdx
+++ b/src/content/docs/test-insights/test-frameworks/golang.mdx
@@ -14,6 +14,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={golangLogo} alt="Golang logo" />
 
@@ -81,9 +82,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/jest.mdx b/src/content/docs/test-insights/test-frameworks/jest.mdx
index d96753ab67..8a097bda60 100644
--- a/src/content/docs/test-insights/test-frameworks/jest.mdx
+++ b/src/content/docs/test-insights/test-frameworks/jest.mdx
@@ -14,6 +14,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={jestLogo} alt="Jest logo" />
 
@@ -105,9 +106,7 @@ After pushing these changes:
 2. A JUnit report (`junit.xml`) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/junit.mdx b/src/content/docs/test-insights/test-frameworks/junit.mdx
index 66eba51726..8d21bb977f 100644
--- a/src/content/docs/test-insights/test-frameworks/junit.mdx
+++ b/src/content/docs/test-insights/test-frameworks/junit.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your JUnit tests and upload
 them to **Test Insights** using your CI workflow.
@@ -91,6 +92,7 @@ For Gradle projects:
 ```yaml
 - name: Run JUnit Tests and Generate Report
   id: tests
+  continue-on-error: true
   run: ./gradlew test
 ```
 
@@ -131,9 +133,7 @@ After pushing these changes:
 2. JUnit XML reports are generated by Maven/Gradle.
 3. The Mergify CI action uploads the reports to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/minitest.mdx b/src/content/docs/test-insights/test-frameworks/minitest.mdx
index 0e3c26a09c..4bb7f993b1 100644
--- a/src/content/docs/test-insights/test-frameworks/minitest.mdx
+++ b/src/content/docs/test-insights/test-frameworks/minitest.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your Minitest tests and upload
 them to **Test Insights** using your CI workflow.
@@ -142,6 +143,7 @@ Using `minitest-reporters` approach:
 ```yaml
 - name: Run Minitest Tests and Generate JUnit Report
   id: tests
+  continue-on-error: true
   run: bundle exec rake test
 ```
 
@@ -169,9 +171,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/mstest.mdx b/src/content/docs/test-insights/test-frameworks/mstest.mdx
index 231cd94c9f..b5035888e2 100644
--- a/src/content/docs/test-insights/test-frameworks/mstest.mdx
+++ b/src/content/docs/test-insights/test-frameworks/mstest.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your MSTest tests and upload
 them to **Test Insights** using your CI workflow.
@@ -115,9 +116,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/nunit.mdx b/src/content/docs/test-insights/test-frameworks/nunit.mdx
index 6cc91adad7..806a14b81c 100644
--- a/src/content/docs/test-insights/test-frameworks/nunit.mdx
+++ b/src/content/docs/test-insights/test-frameworks/nunit.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your NUnit tests and upload
 them to **Test Insights** using your CI workflow.
@@ -134,9 +135,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/pest.mdx b/src/content/docs/test-insights/test-frameworks/pest.mdx
index 1f62f4357e..cd17549b3a 100644
--- a/src/content/docs/test-insights/test-frameworks/pest.mdx
+++ b/src/content/docs/test-insights/test-frameworks/pest.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your Pest tests and upload
 them to **Test Insights** using your CI workflow.
@@ -126,9 +127,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/phpunit.mdx b/src/content/docs/test-insights/test-frameworks/phpunit.mdx
index 5eccd9a4bd..ced507f6b2 100644
--- a/src/content/docs/test-insights/test-frameworks/phpunit.mdx
+++ b/src/content/docs/test-insights/test-frameworks/phpunit.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your PHPUnit tests and upload
 them to **Test Insights** using your CI workflow.
@@ -113,9 +114,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/rust.mdx b/src/content/docs/test-insights/test-frameworks/rust.mdx
index 826af2fbaa..9b250ac2a0 100644
--- a/src/content/docs/test-insights/test-frameworks/rust.mdx
+++ b/src/content/docs/test-insights/test-frameworks/rust.mdx
@@ -14,6 +14,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 <IntegrationLogo src={rustLogo} alt="Rust logo" />
 
@@ -132,9 +133,7 @@ After pushing these changes:
 2. A JUnit report (junit.xml) is generated.
 3. The Mergify CI action uploads the report to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips
 
diff --git a/src/content/docs/test-insights/test-frameworks/testng.mdx b/src/content/docs/test-insights/test-frameworks/testng.mdx
index e59f26292d..c43a36d7ce 100644
--- a/src/content/docs/test-insights/test-frameworks/testng.mdx
+++ b/src/content/docs/test-insights/test-frameworks/testng.mdx
@@ -12,6 +12,7 @@ import BuildkiteCIUploadStep from "../../../../components/BuildkiteCIUploadStep.
 import BuildkiteCIUploadStepMatrix from "../../../../components/BuildkiteCIUploadStepMatrix.astro"
 import BuildkiteCIQuarantineSetup from "./_buildkite_mergify_ci_quarantine_setup.mdx"
 import MergifyCliUploadStep from "../../../../components/MergifyCliUploadStep.astro"
+import ReviewInTestInsights from "./_review-in-test-insights.mdx"
 
 This guide shows how to generate JUnit reports from your TestNG tests and upload
 them to **Test Insights** using your CI workflow.
@@ -146,9 +147,7 @@ After pushing these changes:
 2. JUnit-compatible XML reports are generated.
 3. The Mergify CI action uploads the reports to Test Insights.
 
-You can then review your test results, including any failures or flaky tests,
-directly in the [Test Insights
-dashboard](https://dashboard.mergify.com/test-insights/jobs).
+<ReviewInTestInsights />
 
 ## Troubleshooting Tips