> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/quickstart/create-first-test.md).

# Create Your First Test

Your first TestVibe test should describe one clear user behavior. Keep it small: one page, one action, and one result you can verify.

TestVibe can use this intent to generate Playwright code later.

## Steps

1. Open the **Test Suite**.
2. Create or select a group for the feature area you want to test.
3. Create a new test or feature.
4. Give it a clear name.
5. Write the behavior in Gherkin-style steps.
6. Save the test. It is saved to your project.

If you are unsure how to write the steps, start with a simple `Given`, `When`, `Then` structure. You can also [record browser steps](/create-tests/use-recorder.md), [import existing tests](/create-tests/import-existing-tests.md), or accept an AI suggestion — but for a first test, writing one short scenario is the clearest path.

## Example First Test

```gherkin
Feature: Sign in

  Scenario: User signs in with valid credentials
    Given the user is on the sign-in page
    When the user enters valid credentials
    And the user clicks Sign in
    Then the dashboard should open
    And the user name should be visible in the header
```

This is a good first test because it has:

* a clear feature name
* one scenario
* a visible starting point
* a concrete user action
* an expected result the generated test can verify

## Tips For A Good First Test

Do:

* test a stable, important flow
* use visible text from the application when possible
* include the expected result
* keep the scenario short
* use test data that is available in the target environment

Avoid:

* testing several unrelated flows in one scenario
* using vague phrases like `it should work`
* depending on data that might not exist
* starting with a complex end-to-end flow that requires many setup steps

## Where Gherkin Fits

Gherkin is the plain-language structure TestVibe uses for features, scenarios, and steps. Learn the basics in [Gherkin and feature files](/create-tests/gherkin-and-feature-files.md).

## Next

Continue to [Generate Playwright code](/quickstart/generate-playwright-code.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/quickstart/create-first-test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.