> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tester.army/llms.txt
> Use this file to discover all available pages before exploring further.

# Organize Tests into Groups

> Organize tests into groups for PR regression testing, CI webhooks, and scheduled monitoring - one test can belong to multiple 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. In the **Test library** rail, click **+** next to **Groups**.
3. Enter a clear name, such as `Critical flows`.
4. Add existing tests to the group from each test's **Group** control in the
   **All Tests** view, or use **Add test** while the group is selected to create
   a test directly in it.

Select a group in the rail to see only its tests. Each group has its own
**Run tests** row for [run mode](/run/run-mode), [production
monitoring](/run/production-monitoring), the [preparation test](/run/prep-test),
and its [webhook](/run/group-webhooks).

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 or when a concurrent group should run only a few tests at once, 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.