docs: match UI labels exactly in docs-tests, and fix two casing drifts - #2992
Open
marcel-rbro wants to merge 1 commit into
Open
marcel-rbro wants to merge 1 commit into
marcel-rbro wants to merge 1 commit into
Conversation
marcel-rbro
added
documentation
Contributor
|
✅ Preview for this PR (commit |
marcel-rbro
force-pushed
the
docs/docs-tests-storage-account
branch
from
September 17, 2026 14:27
66dc1b4 to
d5a1f76
Compare
The runner matched element labels with `exact: false`, so an assertion passed whenever the documented label was merely *contained* in what the Console renders. That hides the most common kind of drift: a casing change. Switching the four locators to exact matching turned up two real ones, both of which had been passing silently. - Billing: the docs said **Plan Consumption**; Console renders "Plan consumption". Fixed in the doc, and "Graph" lowercased with it since it is not part of the label. - Settings: the docs said **account-level integrations**; Console renders "Account-level integrations". Both are bolded as UI element names, so house style says they should match the screen. Exact matching stays whitespace-trimmed, so only wording, casing and trailing decoration can break a target — all things the docs should be updated to match. Of 52 UI assertions these two were the only breakages; the rest already matched their labels character for character. Verified against staging: 139 passed, 0 failed, 35 skipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FSj1mTUbMKgmu2JoGJLSKD
marcel-rbro
force-pushed
the
docs/docs-tests-exact-matching
branch
from
September 17, 2026 14:44
30dd708 to
9c3cc1c
Compare
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
2 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 #2671. Stacked on #2989.
The runner matched labels with
exact: false, so an assertion passed whenever the documented label was merely contained in what Console renders. That hides the most common kind of drift — a casing change.Switching the four locators to exact matching found two real ones that had been passing silently:
Both are bolded as UI element names, so house style says they should match the screen. Fixed in the docs and in the baseline targets. ("Graph" lowercased with the first, since it isn't part of the label.)
Exact matching is still whitespace-trimmed, so only wording, casing and trailing decoration can break a target — all things the docs should be updated to match. Of 52 UI assertions these two were the only breakages; the rest already matched character for character.
Verified against staging: 139 passed · 0 failed · 35 skipped.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FSj1mTUbMKgmu2JoGJLSKD