qa-browser checks 5 of 18 pages by default and captures no console errors #227
Labels
No Label
P0
P1
P2
P3
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
phase-7
phase-8
release-blocker
security
seo
ui
ux
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Queue-North-Website#227
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seen at
a25077d(v0.9.5).What is true now.
scripts/qa-browser.mjsdefaults--urlto production (line 60) and--pathsto/,/about,/services,/contactand/support(line 73): 5 of the 18 pages, and none of the service or industry pages this batch changes. It records no console or page errors, so a hydration failure or a thrown effect is invisible to it.What to do. Default the paths to the target's
sitemap.xml, and exit 2 if it cannot be read (nothing checked is not a pass). Capture console errors and page errors per page, as findings. Fixdocs/qa/ClaudeQAPlan.md:85("five widths"; it is four) anddocs/TOOLS.mdto match.Verify:
node scripts/qa-browser.mjs --url http://localhost:3001checks all 18 sitemap pages, and reports a finding when a page logs a console error.Done in
7cd556c. scripts/qa-browser.mjs now defaults its path list to the target's own sitemap (18 pages instead of 5 hand-typed ones, and it exits 2 if it cannot read the sitemap) and captures page errors and console errors as findings. Proven: a console.error added to About produced '/about @390: the page logged an error', and a clean build reports nothing across all 18 sitemap pages. docs/qa/ClaudeQAPlan.md corrected from 'five pages, five widths' to every page in the sitemap at four widths.