# Test your Lovable app with browser journeys

Source: https://docs.qualflare.com/docs/ai/lovable · Last updated: 2026-11-15

Connect Lovable to Qualflare, add your app's preview link as a browser target, and let Lovable save and run browser journeys that report as launches.

To test a Lovable app with Qualflare, connect Lovable to the [Qualflare MCP server](https://docs.qualflare.com/docs/api/mcp) and ask it to save browser journeys, which Qualflare runs on the app's preview link in a hosted browser and files as launches; you need the Editor role on the project.

A **browser journey** is a named list of browser steps, up to 50, for one flow of your app, such as signing in or checking out. Lovable writes the journeys while it builds the app, and Qualflare runs them against the app's Lovable preview: the app as it is now, without publishing. Each run is reported as a normal [launch](https://docs.qualflare.com/docs/runs/launches), so [failure clusters](https://docs.qualflare.com/docs/ai/failure-clusters), [webhooks](https://docs.qualflare.com/docs/integrations/webhooks) and [integrations](https://docs.qualflare.com/docs/integrations) work on it like on any other launch.

| Fact      | Detail                                                                                                                                                                                                              |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Where     | **Journeys** under **Planning** in the project sidebar; **Project Settings** > **Browser Targets** for the apps journeys test                                                                                       |
| Who       | Adding, editing and deleting browser targets, and connecting Lovable: the Editor role or higher in the project. Viewing journeys and runs: the Viewer role or higher in the project                                 |
| Plans     | Each run uses one launch of your plan's [launch quota](https://docs.qualflare.com/docs/reference/glossary#launch-quota)                                                                                             |
| MCP tools | `list_browser_targets`, `list_journeys`, `get_journey`, `create_journey`, `update_journey`, `delete_journey`, `run_journeys`, `get_journey_run`, `cancel_journey_run`, `browser_capabilities` and `testing_context` |

## Before you begin

You need:

* A Lovable app.
* On the Qualflare project the results should go to, the Editor role or higher in the project.
* Launches left in your plan's launch quota for the month: a run that would exceed it doesn't start.

## Add your app as a browser target

A browser target is the Lovable app Qualflare's hosted browser opens, reached through its preview link. Only you add it, in Qualflare: Lovable can't create one, because it never sees the preview link.

1. In Lovable, open **Share** > **Preview link** and create a link. A preview link must be renewed every 7 days; on Lovable's Business plans you can choose "Never" to skip renewing it.
2. In Qualflare, open **Project Settings** > **Browser Targets** and click **Add Lovable app**.
3. Enter a **Name**, such as the app's name. Each target's name is unique in the project.
4. Paste the link into **Preview link**. It starts with `https://lovable.dev/preview/`.
5. Optionally, change **Allowed hosts** and add **Test credentials** (see [Credentials and allowed hosts](https://docs.qualflare.com/docs/ai/lovable#credentials-and-allowed-hosts)).
6. Click **Add Lovable app**.

The preview link and the credentials are encrypted and can never be read back, by you, by Lovable or by anyone else.

*Figure: A browser target holds the app's preview link, the other hosts its pages call, and the test logins journeys use.*

## Connect Lovable to Qualflare

Lovable connects to Qualflare with sign-in, so you copy no token:

1. In Lovable, open **Connectors**, choose **Add custom** > **MCP server**, enter a **Server name** and `https://api.qualflare.com/mcp` as the **Server URL**, keep **OAuth (default)**, and click **Add & authorize**.
2. On the Qualflare page that opens, choose the project that holds your browser target.
3. Leave **Allow changes** ticked: saving and running journeys are changes.
4. Click **Approve**.

The connection then shows under **Connected apps** on **Project Settings** > **Access Tokens**, where you can revoke it. See [Connect with sign-in](https://docs.qualflare.com/docs/api/mcp#connect-with-sign-in) for what a connection can do and how long it lasts.

If you would rather use a token, choose **Bearer token or API key** in Lovable and paste a project access token created with **Allow writes**; the **Lovable** tab of the **Connect a coding agent** panel on **Project Settings** > **Access Tokens** lists the same steps.

## Ask Lovable to create and run tests

Lovable reads Qualflare's instructions when it connects, so you ask for tests in your own words, in the Lovable chat. When an app has a browser target, Qualflare tells Lovable that tests, test cases and test suites for it mean browser journeys.

You might write "Create the test suites this app needs on Qualflare". Lovable lists your browser targets and existing journeys, saves one journey for each user flow it finds, runs them, and tells you the result and the launch number.

After you change the app, write "Run the Qualflare tests again", and Lovable runs the saved journeys on the new preview.

When a journey fails, Lovable's job is to fix the app and run the journey again unchanged, or to update a journey that no longer matches the app; it is told never to weaken an assertion to make a run pass. You can be specific, as in "The sign-in journey failed: fix the app and run it again".

The **Lovable** tab of the **Connect a coding agent** panel also offers a starting prompt to copy:

```text
Use the Qualflare MCP tools: find or create a journey for the main flow of this app (open the home page and check it loads), run it on the preview, and tell me the result. If it fails, fix the app and run it again.
```

If Lovable doesn't seem to know a Qualflare tool, start a new chat: Lovable loads the tool list when a chat starts.

## Check the results

Browser journey results are in two places in Qualflare:

* **Journeys** in the project sidebar has a **Journeys** tab with each saved journey, its target and version, and a **Runs** tab with each run's status, duration and launch. A run goes from queued to running and reporting, and ends passed, failed, error or cancelled. A run's page shows its progress, the step that failed with the page text, and screenshots.
* Each finished run is a launch in the environment **Lovable (preview)**, which Qualflare creates with the project's first browser target. Its results are in a suite named after the target, such as **Browser journeys / My Lovable app**, created by the target's first run, with one test case per journey.

A journey keeps its test case when you rename it, so its history stays in one place. Renaming a target renames its suite too.

## Renew an expired preview link

A Lovable preview link expires unless it was created with "Never". The **Preview** column of **Project Settings** > **Browser Targets** shows each link's state, such as "Connected · 5 days left", "Expiring · 1 day left" or "Expired", and the page warns that "A preview link needs renewing". Journeys on a target with an expired link can't run, and a run refused for this uses no launch.

1. In Lovable, open **Share** > **Preview link** and create a new link.
2. In Qualflare, click **Renew** on the target's row in **Project Settings** > **Browser Targets**.
3. Paste the new link into **Preview link** and click **Renew link**.

The target keeps its journeys, credentials and results.

## Credentials and allowed hosts

**Test credentials** are the logins a journey types, such as a test user's email and password. Each is a key and a value, up to 20 per target. A journey names the key, never the value, and Lovable sees only the key names. Use a test account, never a real person's login.

**Allowed hosts** are the only sites the hosted browser may visit besides your app's preview, which is always allowed. The default is `*.supabase.co`, kept when you leave the list empty; add the other backends your pages call, up to 49 hosts, with `*.example.com` for subdomains. `qualflare.com` and its subdomains are refused. A step that goes anywhere else fails with `navigated outside allowed hosts:` and the host's name.

To change either later, choose **Edit** from the target's actions menu, then **Save changes**.

## Limits

| Limit                                 | Value                                                                  |
| ------------------------------------- | ---------------------------------------------------------------------- |
| Steps in a journey                    | 50                                                                     |
| Journeys on a browser target          | 200                                                                    |
| Journeys in one run                   | 1 to 20, with at most 200 steps in total                               |
| Runs in progress in a project at once | 3                                                                      |
| Launches                              | Each run uses one launch of your plan's quota, reserved when it starts |

A run still unfinished after 1 hour ends with the status error.

## Delete a browser target

> **Caution:** Deleting a browser target deletes its journeys, cancels its runs in progress, and deletes its stored credentials and preview link. This cannot be undone. Past runs, launches and the results suite stay.

Choose **Delete** from the target's actions menu in **Project Settings** > **Browser Targets**, then confirm.

## Troubleshoot

**"This preview link was refused."** — Qualflare could not use the link. Check it in Lovable (**Share** > **Preview link**) and paste it again.

**A run doesn't start because the preview link expired** — [renew the preview link](https://docs.qualflare.com/docs/ai/lovable#renew-preview-link), then ask Lovable to run the journeys again.

**Three runs are already in progress** — wait for one to finish, or ask Lovable to cancel one.

**The launch quota is used up** — the run doesn't start until your quota resets or your plan changes; see [Plans and limits](https://docs.qualflare.com/docs/administration/plans#limits).

**A journey names a credential the target doesn't have** — the run is refused, naming the step, the journey and the key. Add the key under **Test credentials**, or ask Lovable to use one of the keys the target has.

**Lovable can't save or run journeys** — the connection was approved without **Allow changes**, or your role is below Editor. Revoke the app under **Connected apps** and connect again with **Allow changes** ticked.

## Next steps

* [Connect a coding agent (MCP)](https://docs.qualflare.com/docs/api/mcp)
* [Launches](https://docs.qualflare.com/docs/runs/launches)
* [Failure clusters](https://docs.qualflare.com/docs/ai/failure-clusters)
* [MCP server reference](https://docs.qualflare.com/docs/api/mcp-reference)
