docs: move test framework configuration and quarantine to Test Insights#11612
Merged
mergify[bot] merged 1 commit intoMay 21, 2026
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
There was a problem hiding this comment.
Pull request overview
Moves test framework configuration docs and the Quarantine reference from the CI Insights section to the Test Insights section, aligning setup guidance with the Test Insights features that consume test-level data, while keeping CI Insights as the home for CI setup guides and adding redirects for legacy URLs.
Changes:
- Updates sidebar navigation to nest “Quarantine” and “Test Frameworks Setup” under Test Insights instead of CI Insights.
- Adds a “Test Framework Configuration” section (with a framework grid) to
/test-insights, and replaces the CI Insights framework section with a pointer to the new location. - Adds redirects from old
/ci-insights/test-frameworks/*and/ci-insights/quarantineURLs to their new/test-insights/...equivalents.
Reviewed changes
Copilot reviewed 23 out of 26 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/content/navItems.tsx | Moves Quarantine and framework setup nav entries under Test Insights; updates paths to /test-insights/.... |
| src/content/docs/test-insights/test-frameworks/cypress.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/golang.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/jest.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/junit.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/minitest.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/mstest.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/nunit.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/pest.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/phpunit.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/playwright.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/pytest.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/rspec.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/rust.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/testng.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/vitest.mdx | Updates page frontmatter (title/description) to “Mergify”. |
| src/content/docs/test-insights/test-frameworks/_gha_mergify_ci_quarantine_setup.mdx | Adds GitHub Actions quarantine setup guidance (new partial). |
| src/content/docs/test-insights/test-frameworks/_buildkite_mergify_ci_quarantine_setup.mdx | Adds Buildkite quarantine setup guidance (new partial). |
| src/content/docs/test-insights/test-frameworks/_common-troubleshooting-tips.mdx | Adds shared troubleshooting tips (new partial). |
| src/content/docs/test-insights/quarantine.mdx | Updates framework-configuration link to /test-insights#test-framework-configuration. |
| src/content/docs/test-insights/prevention.mdx | Updates framework-configuration link to /test-insights#test-framework-configuration. |
| src/content/docs/test-insights/mitigation.mdx | Updates framework-configuration and quarantine links to /test-insights/.... |
| src/content/docs/test-insights.mdx | Adds “Test Framework Configuration” section with a DocsetGrid of frameworks. |
| src/content/docs/ci-insights/setup/buildkite.mdx | Points framework configuration section to the new Test Insights anchor. |
| src/content/docs/ci-insights.mdx | Replaces framework grid with a pointer to Test Insights framework guides. |
| public/_redirects | Adds redirects for legacy CI Insights framework + quarantine URLs to Test Insights. |
Comments suppressed due to low confidence (15)
src/content/docs/test-insights/test-frameworks/cypress.mdx:3
- The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/golang.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/jest.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/junit.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/minitest.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/mstest.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/nunit.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/pest.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/phpunit.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/playwright.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/pytest.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/rspec.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/rust.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/testng.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
src/content/docs/test-insights/test-frameworks/vitest.mdx:3 - The frontmatter now says this is an integration with Mergify, but the page content still repeatedly refers to uploading results to “CI Insights” (including the opening paragraph). Please align the terminology (either update the body to “Test Insights”/“Mergify”, or keep the title/description as “CI Insights”) so the page is consistent.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Test framework plugins emit test-level data that powers Test Insights (prevention, detection, mitigation), so the per-framework setup pages and the Quarantine reference now live under /test-insights/ alongside the features they enable. Framework page prose and frontmatter are updated to reference Test Insights consistently. CI Insights keeps a pointer paragraph to the new location and the old URLs redirect via public/_redirects. Change-Id: I28c101d6adb746991c85c4a60125dcd0127cb2c7
jd
force-pushed
the
devs/jd/worktree-move-test-insights/move-test-framework-config-quarantine-test--28c101d6
branch
from
a1e54ae to
88d19d6
Compare
Member
Author
Revision history
|
JulianMaurin
approved these changes
May 20, 2026
kozlek
approved these changes
May 21, 2026
Contributor
Merge Queue Status
This pull request spent 2 minutes 23 seconds in the queue, including 1 minute 53 seconds running CI. Required conditions to merge
|
51 tasks
mergify
Bot
deleted the
devs/jd/worktree-move-test-insights/move-test-framework-config-quarantine-test--28c101d6
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Test framework plugins emit test-level data that powers Test Insights
(prevention, detection, mitigation), so the per-framework setup pages
and the Quarantine reference now live under /test-insights/ alongside
the features they enable. Framework page prose and frontmatter are
updated to reference Test Insights consistently.
CI Insights keeps a pointer paragraph to the new location and the old
URLs redirect via public/_redirects.