Update & expand Playwright test coverage #16516
Draft
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
janbrasna
commented
Aug 21, 2025
Comment on lines
-11
to
14
| * URL paths for inclusion in page-level a11y scans. | ||
| * Pages will be scanned at both desktop and mobile resolutions. | ||
| * Different set of pages will be scanned at desktop and mobile resolutions. | ||
| */ | ||
| const desktopTestURLs = [ | ||
| '/en-US/', |
There was a problem hiding this comment.
BTW I've changed the wording because I wasn't entirely sure what list would be used for what, so I hopefully got it right this way. Feel free to suggest any improvements if I'm not making it clear, or getting it completely wrong.
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.
One-line summary
Reinstates some useful tests, and expands the list for a11y coverage.
Significant changes and points to review
There are axe test failures on some of the newly added pages. I'll add the reports for more info. This can either land to deliberately start failing the tests until fixed, or can be added with the exclusions enumerated for now, or can wait to merge until the a11y issues reported are fixed.
Issue / Bugzilla link
#16405
Testing
npm run a11y-teststest-results-a11y.zip