Understand the Test Suite

Learn how the Test Suite organizes groups, feature files, generated code, and test status.

The Test Suite is the main place to create, organize, generate, and run TestVibe tests for the selected project.

It shows your test groups on the left and details for the selected group or feature on the right.

TestVibe Test Suite overview

What The Suite Contains

Item	What it means
Group	A folder-like area for related features, such as Auth, Billing, or Admin.
Feature file	A .feature file that describes behavior in Gherkin.
Scenario	A concrete user behavior inside a feature.
Generated code	Playwright code created from the feature intent.
Generation status	Whether a feature is ready, generating, failed, or needs attention.
Run status	Recent execution status when test results are available.

In your project, feature files usually live under Features/. A group often maps to a folder such as Features/Auth/.

Group View

When you select a group, TestVibe shows a group overview with the features in that area.

From a group, you can usually:

• add a feature

• import feature files

• run the group

• open a feature

• delete selected features when you have permission

• review group readiness and recent activity

Use groups to keep the suite readable. A group should be meaningful to the team, not just a technical folder.

Feature View

When you select a feature, TestVibe shows details for that specific test intent.

Depending on the feature state, you may see:

Area	What it is for
Overview	Summary, file path, status, and available actions.
Editor	The Gherkin source for the feature.
Generation	Live or historical generation progress.
Code	Generated Playwright code when available.
Results	Recent run evidence when the feature has been executed.

Status In The Suite

Status helps you decide what to do next:

Status idea	What to do
Draft or editable	Review and improve the Gherkin before generation.
Generating	Wait for TestVibe to finish or inspect live progress.
Ready to test	Run the generated Playwright test.
Failed generation	Open generation details and fix the input or setup.
Failed run	Review results and decide whether the test or application needs changes.

How To Use The Suite Well

• Keep groups aligned with product areas or user journeys.

• Use feature names that a teammate can understand without opening the file.

• Keep scenarios focused and reviewable.

• Regenerate code when Gherkin intent changes meaningfully.

• Use run results to improve both the app and the test intent.

Related Pages

Create structure

Create groups and tests

Write features

Gherkin and feature files

Generate code

Generate Playwright code