Skip to main content

Generate Tests With Assistant

Assistant generation helps you turn readable test intent into runnable browser automation.

In TestVibe, generation usually starts from a Gherkin feature or a new feature idea. The selected model uses your instructions, target site, and project settings to create or update test output in your project.

What You Can Generate​

What Assistant Generation Does​

It can help withWhat that means
Drafting feature behaviorTurn a user goal into clearer Gherkin scenarios.
Generating Playwright codeCreate executable browser automation from saved test intent.
Using target site contextInspect or interact with the site while building the test.
Showing progressReport useful activity, ask questions, and show verification results and captured evidence.
Iterating on testsRegenerate after you improve the instructions or setup.

What Assistant Generation Does Not Replace​

Assistant generation does not remove the need to review tests.

You still decide:

  • whether the Gherkin describes the right behavior
  • whether the generated code checks the right outcome
  • whether test data and credentials are safe and repeatable
  • whether a failure means the app is broken, the test is wrong, or the setup is incomplete

Before You Generate​

Make sure the project has:

RequirementWhy it matters
Saved feature intentGeneration needs clear behavior to turn into code.
Target site URLThe agent and the cloud test session need a site to inspect or run against.
Available creditsGeneration runs on TestVibe’s metered Assistant service and stops when the balance runs out.
Site reachabilityThe cloud test session must be able to reach the target site.

Start Here​

New to generation? Read How Assistant generation works, then continue to Generate Playwright code.