Add browser coverage for human-readable routes - #252
Conversation
MattIPv4
left a comment
There was a problem hiding this comment.
Thanks for working on this! Instead of unstable_dev, I wonder if we can use the new createTestHarness designed for use w/ Playwright etc.? https://developers.cloudflare.com/changelog/post/2026-07-21-integration-test-harness/
There was a problem hiding this comment.
Instead of a dedicated spec file for the human outputs, I think it'd be good to include this as part of the existing spec files for each route, if possible? Or, if not, at least have a dedicated browser spec file alongside each existing route/spec?
|
Addressed both suggestions: the browser suite now uses Fresh current-base checks pass: Chromium 2/2 twice, unit tests 485/485, types, lint, focused formatting, a Wrangler dry run, and |
Type of Change
What issue does this relate to?
Fixes #188
What should this PR do?
createTestHarness()lifecycle and a same-origin Vite proxy./apidocumentation and/libraries/backbone.js/1.1.0version page whenWEBSITE_BASEidentifies the website origin.Source Mapsfilter and checking the resulting file links.What are the acceptance criteria?
npm testnpm run test:browsernpm run lintnpm run typesnpx wrangler deploy --dry-runThis adds test coverage and cross-platform build normalization; it does not change the rendered UI, so before/after screenshots are not applicable.