Skip to content

fix(test-insights): link the four framework pages that only mentioned the dashboard #12758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 1 commit into from
Sep 10, 2026
+36 −16
Merged

fix(test-insights): link the four framework pages that only mentioned the dashboard #12758

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions src/content/docs/test-insights/test-frameworks/playwright.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ import playwrightLogo from "../../../images/ci-insights/playwright/logo.svg"
import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
import ReviewInTestInsights from "./_review-in-test-insights.mdx"

<IntegrationLogo src={playwrightLogo} alt="Playwright logo" />

Expand Down Expand Up @@ -126,9 +127,6 @@ steps:
The reporter automatically collects your test results and sends them to Test
Insights.

Check the Test Insights dashboard afterward to view execution metrics, detect
flaky tests, and review test trends.

## Multi-Project (Cross-Browser) Runs

If your `playwright.config.ts` defines multiple
Expand All @@ -154,6 +152,13 @@ env:
This option is opt-in (off by default) to preserve the history of tests that
already report without a project prefix.

## Verify and Review in Test Insights

After pushing these changes, your next CI run reports its Playwright results
automatically.

<ReviewInTestInsights />

## Environment Variables

| Variable | Purpose | Default |
Expand Down
15 changes: 10 additions & 5 deletions src/content/docs/test-insights/test-frameworks/pytest.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ import pytestLogo from "../../../images/ci-insights/pytest/logo.svg"
import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
import ReviewInTestInsights from "./_review-in-test-insights.mdx"

<IntegrationLogo src={pytestLogo} alt="Pytest logo" />

Expand Down Expand Up @@ -104,9 +105,6 @@ steps:

The plugin collects your test results and sends them to Test Insights.

Check the Test Insights dashboard afterward to view execution metrics, detect
flaky tests, and review test trends.

## Using with Tox

If you’re using [Tox](https://tox.wiki/) to manage test environments, you can
Expand Down Expand Up @@ -176,6 +174,13 @@ steps:
```

:::tip
Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights, especially when
running multiple Tox environments or using a matrix.
Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights,
especially when running multiple Tox environments or using a matrix.
:::

## Verify and Review in Test Insights

After pushing these changes, your next CI run reports its pytest results
automatically.

<ReviewInTestInsights />
17 changes: 11 additions & 6 deletions src/content/docs/test-insights/test-frameworks/rspec.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ import rspecLogo from "../../../images/ci-insights/rspec/logo.svg"
import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
import ReviewInTestInsights from "./_review-in-test-insights.mdx"

<IntegrationLogo src={rspecLogo} alt="RSpec logo" />

Expand Down Expand Up @@ -84,8 +85,12 @@ steps:

The gem automatically collects your test results and sends them to Test Insights.

Check the Test Insights dashboard afterward to view execution metrics, detect
flaky tests, and review test trends.
## Verify and Review in Test Insights

After pushing these changes, your next CI run reports its RSpec results
automatically.

<ReviewInTestInsights />

## Environment Variables

Expand All @@ -99,11 +104,11 @@ flaky tests, and review test trends.
| `MERGIFY_TEST_JOB_NAME` | Test job name identifier | Optional |

:::tip
The gem auto-activates in CI environments (detected via the `CI` environment
variable). To enable it outside CI, set `RSPEC_MERGIFY_ENABLE=true`.
The gem auto-activates in CI environments (detected via the `CI` environment
variable). To enable it outside CI, set `RSPEC_MERGIFY_ENABLE=true`.
:::

:::tip
Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights, especially
when running multiple test suites or using a matrix strategy.
Use `MERGIFY_TEST_JOB_NAME` to make reports clearer in Test Insights,
especially when running multiple test suites or using a matrix strategy.
:::
9 changes: 7 additions & 2 deletions src/content/docs/test-insights/test-frameworks/vitest.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ import vitestLogo from "../../../images/ci-insights/vitest/logo.svg"
import IntegrationLogo from "../../../../components/IntegrationLogo.astro"
import CIInsightsSetupNote from "../../../../components/CIInsightsSetupNote.astro"
import BuildkiteTokenNote from "../../../../components/BuildkiteTokenNote.astro"
import ReviewInTestInsights from "./_review-in-test-insights.mdx"

<IntegrationLogo src={vitestLogo} alt="Vitest logo" />

Expand Down Expand Up @@ -97,8 +98,12 @@ steps:
The reporter automatically collects your test results and sends them to Test
Insights.

Check the Test Insights dashboard afterward to view execution metrics, detect
flaky tests, and review test trends.
## Verify and Review in Test Insights

After pushing these changes, your next CI run reports its Vitest results
automatically.

<ReviewInTestInsights />

## Environment Variables

Expand Down