Automated Testing

How it works

How Automated Testing works, drawn only from its official release notes.

1. 01

   What it does

   Now automatically generates testing for any rules added or changed directly within apps, ensuring ongoing protection and reliability across versions.

2. 02

   What the release notes list

   Automatic test generation; Integration with code changes; Enhances reliability; Supports rapid development.

3. 03

   Who gets it

   The source does not say which plans include it. Check your workspace before relying on it.

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 Automated Testing working in a real project rather than a sandbox.

   Set up Automated Testing in this project — lovable writes and runs tests for the rules you change. 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

   Review it before you publish

   Automated 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 Automated Testing before I publish. Check automatic test generation and integration with code changes, 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.

3. 03

   Decide whether it fits your project

   Worth five minutes before you wire anything in. Automated Testing sits in Testing, and not every project needs it.

   I am building the project in this workspace. Given that Automated Testing lovable writes and runs tests for the rules you change, tell me honestly whether it fits what I am building, including the cases where I should not use it. If it does fit, give me the single smallest first step.

   Expected outcome

   A direct yes or no with the reasoning, the cases against it, and one first step. Treat a hedged answer as a no.

Frequently asked

• What is Automated Testing?

  Automated Testing is Lovable's Testing feature: Lovable writes and runs tests for the rules you change. Now automatically generates testing for any rules added or changed directly within apps, ensuring ongoing protection and reliability across versions.

• Is Automated Testing GA or in beta?

  Automated Testing is generally available (GA) on Lovable.

• What Lovable plan includes Automated Testing?

  The atlas has not verified which Lovable plans include Automated Testing. Check Lovable's pricing page.

• When did Automated Testing launch?

  Lovable has not published a verified release date for Automated Testing.