Preview and production drift apart
Find routes, assets and requests that work in the editor but return 404, CORS or empty responses on the published domain.
Release QA for Bolt builds
After deploying a Bolt app, open nested routes directly and complete the main action. Use this checklist to review navigation and interface responses. Preflight records visible page and browser-request errors; server configuration needs a separate review.
Review these scenarios before sharing. The automated report records observable issues on the pages you select.
Find routes, assets and requests that work in the editor but return 404, CORS or empty responses on the published domain.
Check whether the product exposes a useful error and retry when the API fails or returns an unexpected shape.
Open nested pages directly and after reload to catch lost state and incorrect redirects.
Use this sequence alongside the report to review behavior that depends on your business rules and data.
The report separates visual polish from full-stack flow breaks so the issues blocking a real visitor are fixed first.
Open a sample reportNo hints or state inherited from the Bolt preview.
Test direct entry, back navigation and refresh.
Capture the response, waiting state and recovery from failure.
Make sure a technical error does not block the entire viewport.
What the run can and cannot prove.
No. We test the published URL—the exact version a client or user receives.
Yes, when they surface in the browser flow, console or network requests. Internal server auditing is out of scope.