Create Your First Test
Pick the group the test belongs in, start from a blank Gherkin file, and write one self-contained scenario — signing itself in with credentials inserted from the project's variables rather than hardcoded, then saving into that group.
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
- Open the Test Suite.
- Create or select a group for the feature area you want to test.
- Create a new test or feature.
- Give it a clear name.
- Write the behavior in Gherkin-style steps.
- 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, import existing tests, or accept an AI suggestion — but for a first test, writing one short scenario is the clearest path.
Example First Test
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.
Next
Continue to Generate Playwright code.