Automatic Test Creation

How it works

How Automatic Test Creation works, drawn only from its official release notes.

1. 01

   What it does

   With this feature, Lovable automatically generates tests when a developer makes changes to an app's business rules and ensures they run successfully before marking the task complete.

2. 02

   What the release notes list

   Automatic test generation; Runs tests for rule changes; Ensures quality assurance; Integrates seamlessly with development flow.

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 Automatic Test Creation working in a real project rather than a sandbox.

   Set up Automatic Test Creation 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

   Automatic Test Creation 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 Automatic Test Creation before I publish. Check automatic test generation and runs tests for rule 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. Automatic Test Creation sits in Testing, and not every project needs it.

   I am building the project in this workspace. Given that Automatic Test Creation 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 Automatic Test Creation?

  Automatic Test Creation is Lovable's Testing feature: Lovable writes and runs tests for the rules you change. With this feature, Lovable automatically generates tests when a developer makes changes to an app's business rules and ensures they run successfully before marking the task complete.

• Is Automatic Test Creation GA or in beta?

  Automatic Test Creation is generally available (GA) on Lovable.

• What Lovable plan includes Automatic Test Creation?

  The atlas has not verified which Lovable plans include Automatic Test Creation. Check Lovable's pricing page.

• When did Automatic Test Creation launch?

  Lovable has not published a verified release date for Automatic Test Creation.