# Create Tests

Use the Test Suite to describe what your application should do before TestVibe turns that intent into Playwright code.

Tests in TestVibe start as readable feature files. You can create them from scratch, import existing `.feature` files, record a browser journey, or accept AI-suggested test ideas.

## What You Can Do

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Understand the suite</strong></td><td>Learn how groups, features, generated code, and status fit together.</td><td><a href="/pages/KFyP2bFH4rdoYqFMEwha">/pages/KFyP2bFH4rdoYqFMEwha</a></td></tr><tr><td><strong>Create tests</strong></td><td>Add groups and feature files that describe user behavior.</td><td><a href="/pages/XexYlPIo3LDGvD8cW94P">/pages/XexYlPIo3LDGvD8cW94P</a></td></tr><tr><td><strong>Write better intent</strong></td><td>Give TestVibe clear steps and outcomes so generation is stronger.</td><td><a href="/pages/33UtbH87hxyFCMYvvFyo">/pages/33UtbH87hxyFCMYvvFyo</a></td></tr><tr><td><strong>Use the recorder</strong></td><td>Capture a browser journey and review the generated Gherkin.</td><td><a href="/pages/OxgJIOH3ZBUQvXu4Ab22">/pages/OxgJIOH3ZBUQvXu4Ab22</a></td></tr><tr><td><strong>Review suggestions</strong></td><td>Use generated test ideas to fill coverage gaps.</td><td><a href="/pages/CuRLZBxCx40LXSVz0Xei">/pages/CuRLZBxCx40LXSVz0Xei</a></td></tr></tbody></table>

## Start Here

If you are new to TestVibe, start with [Understand the Test Suite](/create-tests/test-suite-overview.md), then read [Gherkin and feature files](/create-tests/gherkin-and-feature-files.md).

## Typical Authoring Flow

1. Choose a group for the feature area.
2. Create or import a feature file.
3. Write one or more scenarios in Gherkin.
4. Save the test intent.
5. Generate Playwright code.
6. Run the test and review results.
7. Improve the Gherkin, generated code, or application behavior.

## Good Test Intent

Strong TestVibe tests are:

| Quality    | What it means                                                               |
| ---------- | --------------------------------------------------------------------------- |
| Focused    | Each scenario proves one behavior or journey.                               |
| Visible    | Steps mention UI labels, fields, messages, and outcomes a user can observe. |
| Repeatable | Test data and setup are stable enough to run again.                         |
| Reviewable | Product, QA, and engineering users can understand what is being tested.     |

## Next

Continue to [Understand the Test Suite](/create-tests/test-suite-overview.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/create-tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.