How Assistant Generation Works
Assistant generation is the bridge between readable test intent and executable Playwright automation.
TestVibe starts the work from the app, runs it in an isolated cloud session, and shows progress as the session reports back.
Follow one test through the whole lifecycle: the inputs generation works from, the cloud session that does the work, the live progress view, the files it saves, and what to check afterwards.
The Short Version
- You select or create a Gherkin or Markdown test in Tests.
- You start generation and confirm the site URL or options.
- TestVibe starts a cloud test session.
- The selected Assistant works from your feature intent and target site.
- TestVibe shows a conversation with progress, questions, verification results, and captured evidence.
- Generated files are saved to your project.
- You review the output and run the test.
Generation Inputs
Generation uses several pieces of context:
| Input | Why it matters |
|---|---|
| Feature intent | The Gherkin or test description tells the agent what behavior to create. |
| Target site URL | The agent and generated test need to know which application to use. |
| Website framework | Framework context helps the agent understand app patterns. |
| Reasoning effort | Set in Settings → Assistant Model. Controls how thorough generation is and how many credits it uses. |
| Project settings | Gives generation access to paths, secrets, and variables. |
| Existing test files | Helps generation fit the project's current structure and style. |
Generation Outputs
Generation can produce or update:
| Output | What it is |
|---|---|
| Feature file | The .feature file that describes the test intent. |
| Playwright code | Executable Playwright files, commonly .spec.js or .spec.ts. |
| Progress details | Assistant messages and expandable activity or verification results. |
| Screenshots or preview | Visual evidence captured while the agent works. |
| Run links | Links to run details or generated output when available. |
Live Progress
The generation view can show:
- an overview of the full generation run
- background, scenario, and scenario outline sections
- authored or generated steps
- section status such as queued, running, finalizing, or failed
- live preview screenshots when available
- links to run details, target site, generated paths, or traces
Generation can pause for a question or a proposed change. Answer in the conversation. Use Run in background to leave the view while the job continues.
See Review generation progress.
Where Files Are Saved
Generated output is saved to your project. Feature files usually live under Features/, and generated Playwright code is stored beside or near the feature it belongs to.
For file management details, see Manage generated test files.
What To Do After Generation
After generation succeeds:
- Read the generated output.
- Confirm it matches the intended behavior.
- Run one test before running a full group.
- Use results to decide whether to keep, edit, or regenerate.
If generation fails, open the generation details first. The failure may be setup-related rather than a problem with the feature itself.