Sample finding · local fixture · redacted
What NightlyQA files when a page breaks
This is a real golden-map walk of a local fixture app, not a customer or dogfood site. The fixture's sign-up page calls an API that returns HTTP 500 and logs a console error. Both leak credential-shaped test values, so you can see NightlyQA redact them before anything is written to the evidence pack.
- Workflow
- golden-map
- Step
- reach:/signup
- Error class
- server-error
- Browser
- Chromium 153.0.8010.12
- Generated
- 2026-11-15 by
node scripts/gen-sample-finding.cjs
Screenshot

Repro steps
open http://fixture.local/signup and watch network
Console excerpt
[
{
"type": "error",
"text": "Failed to load resource: the server responded with a status of 500 (Internal Server Error)"
},
{
"type": "error",
"text": "plans request failed with HTTP 500 (Authorization: Bearer [redacted]"
}
]Network excerpt
[
{
"url": "http://fixture.local/api/plans?token=[redacted]&password=[redacted]",
"status": 500,
"type": "fetch"
}
]The GitHub issue body, as NightlyQA would file it
Issue filing was dry-run for this sample. The full pack also has a video, the page DOM and a metadata file; those stay in the evidence store.
Filed by NightlyQA (AI QA agent). nw-sig: af18dff86e68 ## What broke Workflow **golden-map**, step **reach:/signup**: 5xx from http://fixture.local/api/plans?token=[redacted]&password=[redacted] ## Expectation vs actual Expected: no 5xx on golden page Actual: HTTP 500 ## Repro ``` open http://fixture.local/signup and watch network ``` **Evidence pack:** not published (local pack only; dry-run or no token) - screenshot: golden-map-reach-signup.png - video: golden-map-reach-signup.webm - console: golden-map-reach-signup.console.json - network: golden-map-reach-signup.network.json - dom: golden-map-reach-signup.dom.html - repro: golden-map-reach-signup.repro.txt --- Severity: high First seen: 2026-11-15T19:12:16.295Z Run-tagged data: `nw-sample-fixture` Environment: http://fixture.local | 153.0.8010.12 | sha unknown | nightlyqa v0.1.0