Skip to main content

Test

Help URL: /reference/forms/test

Purpose​

Author a test (a Gherkin .feature) and generate the matching Playwright .spec.ts for it. In TestVibe a test is a feature: you describe the behavior in plain-language Gherkin, then TestVibe generates the runnable Playwright code.

Quick Start​

  1. In the Features view, choose a group, then New feature (start blank with a starter outline, or Record in browser).
  2. Give the feature a name.
  3. Write the behavior as Gherkin in the Gherkin tab (Scenarios with Given/When/Then steps).
  4. Click Generate and pick the testing Site URL to generate against.
  5. Watch live progress in the generation drawer; the generated Playwright code appears under the Code tab.

How Generation Works​

When you generate, TestVibe dispatches a first-party AI agent to an isolated cloud session (or, optionally, your own browser via the recorder extension — the generated test always replays in the cloud). It reads your Gherkin, explores the live site (and your connected source code if you've linked it in Settings → App Repository), and writes the generated Playwright .spec.ts back into your project. Generation is metered in credits.

Groups​

  • Features are organized into groups (folders) in the Features view; create a group, then add features under it.
  • Renaming a group or feature updates it everywhere — all project content lives in TestVibe's cloud, not in a Git repository.
  • See TestGenerationGroupsInfo for how generation scope maps to groups.

Writing Good Steps​

  • Keep each step focused (one user action or one assertion per step).
  • Include critical assertions explicitly (for example: "Then I should see ...") so generation doesn't have to guess.
  • Prefer concrete UI references (for example: "When I click the Save button") over vague descriptions.
  • Start the first step on the site's landing page (home or login).
  • Reference any {{variables}} or {{secrets}} your steps need; set them in Settings → Variables & Secrets.
  • View/edit code: Use the Code tab to open the generated spec in the Editor.
  • Record steps: Use Record in browser to capture a real journey with the TestVibe Recorder extension and turn it into Gherkin or a runnable spec (Recorder (Playwright)).
  • Tidy Gherkin: The editor offers Format and Tidy with AI for the Gherkin source.

Troubleshooting​

  • Duplicate feature name: change the feature name and/or group so it's unique within the group.
  • Generation cannot start: confirm any variables or secrets your steps reference are set in Settings → Variables & Secrets, and that the Site URL is reachable.
  • Out of credits: generation is metered — top up in Settings → Billing.

Notes​