Create Groups and Tests

Add groups and feature files to organize user journeys in the Test Suite.

Create groups and tests when you want to add new behavior to the Test Suite.

In TestVibe, a "test" usually starts as a Gherkin feature file. The generated Playwright code comes later.

Create A Group

Use a group for a product area, workflow, or feature family.

Good group examples:

Group	Good when
Auth	Tests cover sign-in, sign-out, password reset, and account access.
Billing	Tests cover invoices, payment methods, and subscription changes.
Admin	Tests cover administrator-only workflows.

To create a group:

1. Open the Test Suite.

2. Choose the action to add a group.

3. Enter a short, readable group name.

4. Save or confirm.

TestVibe stores group structure in your project, usually under Features/.

Create A Feature In A Group

1. Select the group where the feature belongs.

2. Choose Add Feature.

3. Enter a file-friendly feature name.

4. Review the starter Gherkin.

5. Edit the Feature and Scenario text.

6. Save the feature.

TestVibe creates a .feature file for the new test intent.

Naming Tips

Use names that describe user behavior:

Better	Weaker
User signs in with valid credentials	Login test
Admin creates a new team member	Admin flow
Customer downloads an invoice PDF	Invoice stuff

The name may become part of the file path, so keep it concise and avoid temporary labels.

Rename, Move, Or Delete

Depending on your permissions and the selected item, TestVibe may let you:

Action	What happens
Rename a feature	The feature file is renamed in your project.
Move a feature	The feature file moves to a different group folder.
Rename a group	Feature files in that group move to the new group path.
Delete a feature	The feature file is removed from the test suite.
Delete a group	The group and its features may be removed after confirmation.

Be careful with rename and delete actions. They affect project files, and dependent tests may also be affected.

Create Dependent Tests

If one feature should build on another, use a dependent test instead of copying long setup steps everywhere.

For example, a "Create customer" test might be a prerequisite for "Edit customer billing settings." See Use prerequisites and dependencies.

Next

After creating a feature, improve the Gherkin with Write good test instructions.