Test your app in a browser

1. 1

   Make sure you are viewing the preview of the project you want to test.

   Lovable will always test the exact version of your app that you are currently looking at in the preview.

2. 2

   In your Lovable project chat, ask Lovable to verify something specific about your app.

   This tells Lovable to use browser testing to check the functionality you're interested in. You can use phrases like 'verify it works', 'make sure it works', 'test this', or 'check if it's working'.

3. 3

   If your app requires a login and uses Lovable's built-in backend, specify which user to sign in as if there are multiple options.

   Lovable can sign in to test pages behind a login, but it needs to know which user account to use if it's not obvious.

4. 4

   Monitor the 'Details view' in the project chat while Lovable is testing.

   This view shows you what Lovable is doing, including screenshots, clicks, and any issues it finds, helping you understand the testing process.

Use browser testing to verify the sign-up flow works.

Browser testing

This is when Lovable opens your app in a real web browser, just like a person would, to click buttons, fill out forms, and check if everything works correctly.

Virtual environment

This is a simulated computer setup where the browser testing happens, separate from your own computer, ensuring it doesn't interfere with your work.

Preview

This is the live, working version of your app that Lovable shows you as you build it, allowing you to see changes instantly.

Authentication

This is the process of verifying who a user is, usually by asking for a username and password to log into an app.

Built-in backend (Cloud)

This refers to the parts of your app that run on Lovable's servers, handling things like user accounts and data storage, without you needing to set up your own server.

Test environment

This is a separate version of your app used for testing new features or changes before they are made available to all users.

Live environment

This is the version of your app that real users interact with.

• Don't ask Lovable to make a big change and test it in the same prompt, as you might lose work if the testing gets stuck and you stop it. Build first, then test.
• Be explicit if there are parts of your app that Lovable should not click or interact with during testing, especially if it involves sensitive actions or data.
• Browser testing is slower than other verification methods because it's interacting with a real browser, so be patient.