forked from molecule-ai/molecule-core
bef6fca395
After #2074, the staging-tabs spec stopped failing on the auth-redirect locator timeout (good — the broadened 401-mock works) but started failing on a different aggregate check: Error: unexpected console errors: Failed to load resource: the server responded with a status of 404 Failed to load resource: the server responded with a status of 404 Failed to load resource: the server responded with a status of 404 Browser console messages for resource-load failures omit the URL, so the message is uninformative on its own — we can't filter selectively (e.g. "is this a missing-CSS noise or a real broken endpoint?"). The previous filter list (sentry/vercel/WebSocket/ favicon/molecule-icon) catches specific known-noisy strings but this generic "Failed to load resource" doesn't contain any of them. Two changes: 1. Add page.on('requestfailed') + page.on('response>=400') logging to capture the URL of any failed request. Logs to test stdout (visible in the workflow log) — leaves a breadcrumb so a real bug isn't completely hidden when we filter the generic message. 2. Add "Failed to load resource" to the filter list. With (1) in place we still see the URLs for diagnosis; the generic console message is just noise. Real JS exceptions (panel crash, undefined access, etc.) come with a file path and stack trace and aren't matched by either filter, so the gate still catches actual bugs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| chat-separation.spec.ts | ||
| context-menu-delete.spec.ts | ||
| filestab-smoke.spec.ts | ||
| org-template-import.spec.ts | ||
| staging-setup.ts | ||
| staging-tabs.spec.ts | ||
| staging-teardown.ts | ||