Browser Testing

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Browser Testing working in a real project rather than a sandbox.

   Set up Browser Testing in this project — real-browser interaction with screenshots and network logs. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Verify a checkout flow after a refactor

   The record lists this as one of the jobs Browser Testing is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Browser Testing for verify a checkout flow after a refactor. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Browser Testing is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Browser Testing before I publish. Check real-browser clicks, inputs, navigation and screenshot capture and visual diffs, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Confirm auth still works for a logged-in user

   A second job the record lists for Browser Testing, useful once the first path works.

   Extend this project so Browser Testing also covers confirm auth still works for a logged-in user. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Browser Testing?

  Browser Testing is Lovable's Testing feature: Real-browser interaction with screenshots and network logs. Browser Testing runs your app in a real, remote browser in a virtual environment.

• Is Browser Testing GA or in beta?

  Browser Testing is generally available (GA) on Lovable.

• What Lovable plan includes Browser Testing?

  Browser Testing is available on all Lovable plans.

• When did Browser Testing launch?

  Browser Testing launched on Feb 5, 2026.

• Browser Performance ToolsSame category, also GA · Apr 2026
• Generate files and analyze dataSame category, also GA · Apr 2026
• Project MonitoringSame category · May 2026