Generate Playwright Code

Generate runnable Playwright automation from a saved TestVibe feature file.

Generate Playwright code when your feature intent is ready and you want a runnable browser test.

The generated code is stored in your project and can be run from TestVibe.

TestVibe generates standard Playwright tests. See the official Playwright documentation for the full API and testing concepts.

Before You Generate

Confirm:

Check	Why it matters
The feature is saved	Generation uses the saved project version of the feature.
The Gherkin is clear	Better intent produces better code.
The target site URL is reachable	The cloud test session and generated test need to open the app.
Required secrets exist	Login credentials the test needs must be available in Settings > Variables & Secrets.

Steps

1. Open the Test Suite.

2. Select the feature you want to generate.

3. Start the generation action from the feature details or test list.

4. Confirm the site URL and options.

5. Keep the default reasoning effort unless your team has a reason to change it.

6. Start generation.

7. Stay on the generation progress view until it finishes.

8. Open the generated output after success.

What TestVibe Generates

Generation can create or update:

Output	Purpose
Playwright test file	The browser automation that runs the scenario.
Supporting output	Helpers, configuration use, or generated metadata when needed.
Evidence during generation	Screenshots, section progress, and trace links when available.
Project changes	Generated files saved to your project.

Review Before Running

Before running the generated test, check:

• it follows the intended journey

• it uses the right target page

• it verifies the expected result

• it does not depend on private or accidental data

• it does not ignore important setup from the Gherkin

For more detail, see Read generated output.

If The Output Is Not Right

Do not keep regenerating blindly. First improve the feature:

Problem	Better next step
Test clicks the wrong thing	Add visible labels or clearer page context to the Gherkin.
Test misses the assertion	Add a stronger Then step.
Test needs setup	Add Background, a prerequisite, or test data instructions.
Site could not be reached	Fix the URL, or use a tunnel device for private apps.
A secret token is missing	Add the value in Settings > Variables & Secrets and match the {{secret:NAME}} token.

Then regenerate. See Regenerate a test.