Does Lovable, Replit or Bolt test your published site?
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.
First published ·Facts checked
What each builder’s docs say
Built-in browser testing in Lovable, Replit and Bolt, quoted from their docs (checked October 22, 2026)Scroll sideways for more columns.
Builder
Built-in browser testing, in the docs’ words
Where the docs say 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 lets Agent test its apps “using an actual browser”, and it “automatically fixes any issues that crop up”. “Free Mode keeps App Testing off”
“a browser preview within the Agent pane”; listed for Full Stack JavaScript and Streamlit apps
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: browser testing runs against the preview
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: App Testing runs in the Agent pane
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.
Bolt: no built-in browser testing described
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”.
An unmentioned feature is unknown, not absent. Bolt may describe or add testing after the date above; check its docs before relying on this.
When builder testing fits, and when to check the published site
Builder testing fits when
You are still building and want the builder’s agent to test as it goes: Lovable’s browser testing and Replit’s App Testing are described for that loop.
You want fixes made in the same chat that built the app; Replit says App Testing “automatically fixes any issues that crop up”.
The change is small and you will open the published site yourself before sharing it.
A separate check of the published site fits when
You are about to share the published URL and want evidence from the site visitors open, not the preview.
You build with Bolt, whose pages read describe no built-in browser test, or with Replit in Free Mode, where the docs say App Testing is off.
You want results at desktop, phone and narrow widths with accessibility checks, and a retest of the same failure after a fix. Sybqa does this from a link; other tools in the AI website QA roundup also accept a URL.
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.
What this page does not claim
Every builder quote above was read on October 22, 2026 from the builder’s own documentation. Vendor docs show what a vendor describes, not measured effectiveness, and an unmentioned feature is unknown, not absent. We have not measured how many issues any builder’s testing finds, and this page makes no claim that a check of the published site finds more.
Common questions
Does Lovable test the published site?
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.
Is Replit App Testing on in Free Mode?
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”.
Does Bolt have built-in browser testing?
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.
If my builder tested the preview, should I check the published site?
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.