> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.tester.army/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.tester.army/_mcp/server.

# Organize Tests into Groups

Groups collect tests that should run together. Create groups around a purpose, such as `Critical flows`, `Checkout`, or `Release smoke tests`.

Groups are required for:

* Pull request regression testing.
* CI and deployment webhooks.
* Scheduled production monitoring.
* Running several tests with one action.

## Create a group

1. Open your project and select **Tests**.
2. Create a **New Group**.
3. Enter a clear name, such as `Critical flows`.
4. Add existing tests to the group from each test's **Groups** control.

A test can belong to more than one group. This lets a checkout test run in both `Critical flows` and `Payments` without duplicating the test.

## Choose the right scope

Keep groups focused on one release decision or operational concern:

| Group               | Example contents                  | Useful trigger          |
| ------------------- | --------------------------------- | ----------------------- |
| Critical flows      | Login, checkout, account access   | Every pull request      |
| Release smoke tests | Navigation, signup, core workflow | Deployment pipeline     |
| Production checks   | Login and read-only health checks | Scheduled monitoring    |
| Payments            | Upgrade, invoice, cancellation    | Payment-related changes |

Avoid one large group containing every test. Smaller groups make failures easier to understand and let you run only the relevant coverage.

## Enabled and disabled tests

Automated group runs execute enabled tests and skip disabled tests. Disabled tests remain available for manual runs.

## Configure group execution

Groups run tests concurrently by default. Use [Run Mode](/run/run-mode) when tests must execute sequentially, and add a [Preparation Test](/run/prep-test) when web tests should share authenticated or seeded browser state.

## Add a trigger

After a group runs successfully by hand, choose how it should run automatically:

* Select it under [GitHub pull request regression testing](/run/pr-regression-testing).
* Enable its [signed webhook](/run/group-webhooks) for GitLab CI or another deployment pipeline.
* Select it in [Production Monitoring](/run/production-monitoring) for recurring checks.