Skip to main content

Create Tests

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

Tests start as Gherkin or Markdown instructions. Write them yourself, ask the Assistant to draft them, import a document or issue, record a browser journey, or review a suggested test.

What You Can Do​

Understand the suite

Learn how groups, features, generated code, and status fit together.

Create tests

Add groups and feature files that describe user behavior.

Write better intent

Give TestVibe clear steps and outcomes so generation is stronger.

Use the recorder

Capture a browser journey and review the generated Gherkin.

Start Here​

If you are new to TestVibe, start with Tests overview, then read Gherkin and feature files.

Typical Authoring Flow​

  1. Choose a group for the feature area.
  2. Create or import a feature file.
  3. Write Gherkin scenarios or Markdown steps and expected results.
  4. Save the test intent.
  5. Generate Playwright code, or choose an Assistant run to follow the saved instructions directly.
  6. Run the test and review results.
  7. Improve the Gherkin, generated code, or application behavior.

Good Test Intent​

Strong TestVibe tests are:

QualityWhat it means
FocusedEach scenario proves one behavior or journey.
VisibleSteps mention UI labels, fields, messages, and outcomes a user can observe.
RepeatableTest data and setup are stable enough to run again.
ReviewableProduct, QA, and engineering users can understand what is being tested.

Next​

Continue to Tests overview.