Test your app in a browser
Lovable can open your app in a virtual browser to click buttons, fill forms, and take screenshots. This helps you confirm that your features actually work from a user's perspective.
Anyone who wants to confirm a flow works or troubleshoot an interactive bug in their app preview.
Do this, in order
- 1
Finish building your feature first before asking Lovable to test it.
Asking Lovable to make a large change and test it in one prompt can cause you to lose your work if testing gets stuck and you stop it.
- 2
Ask Lovable to test the specific action in your project chat using phrases like 'Use browser testing to verify...' or 'Test this flow'.
Browser testing is selective and slower than normal code edits, so explicit prompts trigger it reliably.
- 3
Specify who to log in as or make sure you are signed in on the preview if testing pages behind a login.
Lovable tests behind logins using the built-in backend, running as the signed-in preview user or asking you for permission first.
- 4
Click the activity card in the project chat to open the Details view.
This allows you to see the actual screenshots, clicked elements, and console results as Lovable tests your app.
Paste this into your project
Use browser testing to verify the sign-up flow works. Check that all form inputs accept text, submit the form, and verify that it redirects properly without runtime errors.
Words decoded
- Browser testing
- An automated system where an AI controls a real web browser to click buttons, type text, and take pictures of your app just like a human visitor.
- Console logs
- A hidden list of status messages and technical errors recorded by the browser while running your app.
- Runtime errors
- Problems or crashes that only show up while someone is actively using the app, rather than errors spotted beforehand in the code.
Where people get stuck
- Do not bundle a big code change and browser testing into the same prompt; separate them into building first and testing second.
- Do not expect browser testing behind a login to work if you use an external Supabase database or custom authentication instead of the built-in backend.
- Do not rely on browser testing for drawing canvases, complex file uploaders, drag-and-drop tools, or subtle color and design checks.
- Icon-only buttons without text or labels can confuse the browser tester; use clear text labels when possible.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.