> 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/run-tests/run-group.md).

# Run a Group

Run a group when you want more coverage than a single scenario without executing the entire suite. Groups are useful for smoke checks around one feature area, such as sign-in, checkout, billing, onboarding, or admin workflows.

## Before you start

Make sure the group contains generated Playwright tests. TestVibe can select Gherkin feature files, but a run can only execute tests that have runnable Playwright code.

Also confirm:

| Item              | What to check                                                                                       |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| Site URL          | The URL should point to the environment you want the group to test.                                 |
| Shared setup      | Tests in the group should agree on login state, seed data, and dependencies.                        |
| Run configuration | Choose the browser and viewport combination you want to validate.                                   |
| Site access       | The cloud test session must be able to reach the target site; use a tunnel device for private apps. |

## Run from Features

1. Open **Features**.
2. Select the group you want to run.
3. Choose the group run action.
4. Review the selected tests.
5. Confirm the **Environment**.
6. Select one or more **Run Configurations**.
7. Start the run.

When TestVibe opens the run form from a group, the tests in that group are preselected so you can confirm the scope before starting.

## Run from Runs

1. Open **Runs**.
2. Select **New Run**.
3. Check the group in the test list.
4. Add or remove individual tests if you need to adjust the scope.
5. Under **Environment**, pick the environment to run against (or a Custom URL).
6. Select one or more **Run Configurations**.
7. Start the run.

Checking a group selects its child runnable tests. Clearing the group removes those tests from the run selection.

## Review grouped results

After the run starts, the run details page shows live progress and then the final results. Use the grouped result rows to answer three questions:

| Question                   | Where to look                                                     |
| -------------------------- | ----------------------------------------------------------------- |
| Did the feature area pass? | Overall run status and pass/fail counts.                          |
| Which scenario failed?     | Failed test rows in the Tests tab.                                |
| Why did it fail?           | Screenshots, videos, traces, console output, and network details. |

For a larger validation pass, see [Run the full suite](/run-tests/run-full-suite.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/run-tests/run-group.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.