Comparison · AI app builders
Lovable, Replit and Bolt build and publish apps from a chat, and two of them describe a built-in browser test. This page quotes what each builder’s own documentation says that testing covers, word for word and with the date we read it, so you can see whether it reaches the site your visitors open. We make Sybqa, a separate checker that starts from a URL; the builders’ docs are the source for every builder claim here.
Have a site ready to check? Test my site free. 10 browser runs a month after sign-up, without AI review. Add your URL and review a test plan before starting a run. See a sample report first.
First published · Facts checked
| Builder | What the vendor describes | Where it runs |
|---|---|---|
| Lovable | “Browser testing always runs against the preview of the project you are currently working on” | The preview of the project you are working on |
| Replit | App Testing uses “an actual browser” and fixes issues it finds. Monitoring Agent can “detect production issues, investigate the cause, validate a fix, and publish it automatically”. | App Testing: browser preview in the Agent pane. Monitoring Agent: the published app, with auto-publish as a separate setting |
| Bolt | Not described on the pages read. The testing advice found is “Finish and test each layer of your project before you start the next” | No built-in browser test is described on the pages read |
Lovable’s browser-testing docs say: “Browser testing always runs against the preview of the project you are currently working on” (checked October 22, 2026). That is a useful check while you build. The docs describe the preview, not the published site, so a check of the published URL your visitors open answers a separate question.
Replit’s App Testing docs say Agent tests the apps it builds “using an actual browser”, shown as “a browser preview within the Agent pane”, and that it “automatically fixes any issues that crop up”. They also say “Free Mode keeps App Testing off”, and list App Testing for Full Stack JavaScript and Streamlit apps (checked October 22, 2026).
The docs describe a browser preview inside the workspace while Agent builds. A check of the published URL answers a separate question.
Replit’s October 22, 2026 Monitoring Agent announcement describes a different production loop: it can “detect production issues, investigate the cause, validate a fix, and publish it automatically”. Replit says auto-publish is a setting, so this page does not assume it is enabled. That is useful operational automation; it still does not make the builder’s own check an independent release record.
Bolt’s support docs and pricing page, read October 22, 2026, describe no built-in browser or app testing. The testing advice found there is “Finish and test each layer of your project before you start the next”.
These are not exclusive: keep the builder’s testing while you iterate, then check the published URL before a release. The website testing checklist for AI-built apps lists what to look at. If you build with Lovable, test your published Lovable site and send the fix brief back shows the loop step by step.
Its browser-testing docs say “Browser testing always runs against the preview of the project you are currently working on” (checked October 22, 2026). They describe the preview, not the published site.
No. Replit’s App Testing docs say “Free Mode keeps App Testing off” (checked October 22, 2026). When it is on, Agent tests “using an actual browser”, shown as “a browser preview within the Agent pane”.
Replit’s Monitoring Agent can investigate, validate and publish a fix when its production automation is enabled. Sybqa answers a different question: does the published URL pass a reviewed, repeatable check from an independent system, including the widths and accessibility checks in the plan? We have not measured which catches more issues.
Bolt’s support docs and pricing page, read October 22, 2026, describe none. The testing advice found is “Finish and test each layer of your project before you start the next”. An unmentioned feature is unknown, not absent, so check Bolt’s docs for changes.
The builders’ docs describe testing a preview or a browser inside the workspace. The published URL is the one visitors open, so a check there answers a different question. Whether it is worth doing depends on what the release changes; the website launch checklist lists what to look at.
Explore bugs, UI consistency and user journeys from a reviewed plan. Inspect browser evidence and visual review leads in the report. The free plan gives 10 runs a month without AI review after you sign up. See pricing.
Add your site link here and it will be waiting in the console after you create an account. Then describe one journey to check and review the test plan before any run starts.