[pmonfort]

Pull Request Checklist

• Have you read the contributing guidelines?
• Have you read "How to write the perfect pull request"?
• Have you added tests for any changed functionality?
• Have you added the Jira issue number as the first thing in your pull request title (e.g. AO3-1234 Fix thing)
• Do you have fewer than 5 pull requests already open? If not, please wait until they are reviewed and merged before creating new pull requests.
• I acknowledge that submitting code created or modified with the help of AI is a bannable offense.

Issue

XXXXXX

Purpose

Proof of concept from the Slack discussion about checking that i18n PRs don't change any rendered text. Draft so we can discuss over real code.

It adds Playwright using the aria snapshots feature, which compares a page's visible text and elements without using screenshots. The baseline is a YAML file committed to the repo. When a PR changes any rendered text or element the build fails, and if the change is intentional the contributor runs a command to regenerate the YAML. It also catches the forgotten _html case, since the escaped markup shows up as literal text.

The proof of concept covers one test for the new work form and an informational CI job that boots the app with the db:otwseed fixtures, so baselines are deterministic and match CI. The whole job takes about 2 minutes, most of it booting the app. One consideration is that this adds a Node toolchain to the CI. More details in playwright/README.md

Testing Instructions

No user-facing changes. To try it locally, follow playwright/README.md: start a seeded test server and run npm run test:playwright against it. To see the failure mode, change any visible string in the work form views and run it again.

References

Slack discussion in #ao3-coders about reviewing i18n PRs.

Credit

Pablo Monfort (he/him)