Groups allow you to organize your checks and centralize settings like base URL’s, headers, variables and other properties a collection of checks can share.
Example use cases for groups are organizing your checks around:
- A common URL endpoint
- A specific team
- A specific feature in your app
- A test suite; trigger all checks after a deployment
The screenshot below gives a quick overview of the groups' key features.
- Activate and mute all checks in a group
- Configure shared settings for all checks in the group
- API check defaults like headers, assertions and setup & teardown scripts
- Environment variables
- Data center locations
- Alert setting and alert channels
- CI/CD triggers
- Run all checks in one go with a configurable concurrency.
- Tweak checks in the inline “mini editor” to quickly build up a group of similar checks
- Use a common base URL for your API checks
How we run grouped checks
It helps to understand how we run the checks in a group, specifically if you’re doing more sophisticated checks with shared variables, script and alerting channels. Here are the rules:
- Checks are scheduled as individual checks, not “as a group”.
- Calling a “group run” using a trigger (either command line or via our GitHub integration) runs all the checks in a group.
- The group itself does not have an explicit runtime state.
- There are no results or metrics collected at the group level.
- Checks in a group still have their individual scheduling settings.
As you can see, groups in their current incarnation are mostly handy configuration buckets for common properties. In the future we will expand the group features to make them smarter.
You can contribute to this documentation by editing this page on Github