fix(test-insights): link the four framework pages that only mentioned the dashboard - #12758
Open
flagendijk89 wants to merge 1 commit into
Conversation
… the dashboard pytest, playwright, rspec and vitest each ended a reader's setup with an unlinked sentence — "Check the Test Insights dashboard afterward to view execution metrics, detect flaky tests, and review test trends" — buried in the middle of the CI workflow section. The other eleven framework pages close with a "Verify and Review in Test Insights" section carrying the actual dashboard link. These four are the section's second page shape: they use a reporter, plugin or gem that uploads directly with MERGIFY_TOKEN rather than generating a JUnit report for the Mergify CI action to upload. That is why the shared partial never reached them, and it is the same four pages missing a Troubleshooting section. Each now closes with the shared `_review-in-test-insights.mdx` partial under the same heading the other eleven use, preceded by a line naming what just happened so the partial's "You can then review..." has an antecedent. The shared troubleshooting partial is deliberately not added here. It is written for the JUnit path — it talks about `report_path`, the CLI upload step and workflow `if` conditions — and none of these four pages reference any of that. Closing that gap needs framework-specific content rather than a shared block. Also normalises `:::tip` bodies in pytest and rspec to the 2-space indent the rest of the docs use, and rewraps them to the surrounding column. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Change-Id: I7df67cc209a1cded4473b4667caf1653c7a8f73e Claude-Session-Id: 18413631-aa75-4182-9e79-4c1ce31bb683
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
approved these changes
Sep 9, 2026
kozlek
approved these changes
Sep 9, 2026
Contributor
Merge Queue Status
|
65 tasks
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
3 participants
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.
Part of MRGFY-8998 — design polish review, August 2026.
pytest, playwright, rspec and vitest each ended a reader's setup with an
unlinked sentence — "Check the Test Insights dashboard afterward to view
execution metrics, detect flaky tests, and review test trends" — buried
in the middle of the CI workflow section. The other eleven framework
pages close with a "Verify and Review in Test Insights" section carrying
the actual dashboard link.
These four are the section's second page shape: they use a reporter,
plugin or gem that uploads directly with MERGIFY_TOKEN rather than
generating a JUnit report for the Mergify CI action to upload. That is
why the shared partial never reached them, and it is the same four pages
missing a Troubleshooting section.
Each now closes with the shared
_review-in-test-insights.mdxpartialunder the same heading the other eleven use, preceded by a line naming
what just happened so the partial's "You can then review..." has an
antecedent.
The shared troubleshooting partial is deliberately not added here. It is
written for the JUnit path — it talks about
report_path, the CLI uploadstep and workflow
ifconditions — and none of these four pagesreference any of that. Closing that gap needs framework-specific content
rather than a shared block.
Also normalises
:::tipbodies in pytest and rspec to the 2-space indentthe rest of the docs use, and rewraps them to the surrounding column.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
🤖 Generated with Claude Code