test: fix What's New heading assertion - #29
Merged
Conversation
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
1 participant
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.
Summary
Root cause
PR #28 moved What's New into the top-level documentation navigation and added
an exact accessible-name assertion. Zudoku renders an anchor inside the H1, so
Playwright sees the accessible name as
What's New Link to whats-newratherthan exactly
What's New. The page rendered correctly, butpnpm run validatefailed and blocked the docs deployment workflow.Impact
This restores the site validation and deployment path without changing
documentation content or production behavior.
Validation
pnpm run validatetests passed