📄️ Overview
Collections help with monitoring end-to-end workflows or help with executing same tests/monitors on several environments.
📄️ Manage Collections
Collections can help with verifying an end-to-end application flow by executing one or more tests in a sequence.
📄️ Collection execution
Collections are ordered list of monitors/tests that are executed in the sequence they are defined in. A Collection by itself doesn't have failure states, it's just a container shell for executing your underlying tests.
📄️ Collection Results
A Collection is a container for tests. Collection itself doesn't have a pass/failed state, only the underlying steps in a Collection will evaluate any assertions.
📄️ Multi-environment monitoring
Collections also enable you to run same monitoring checks on multiple environments(like Dev/Staging/Prod) without duplicating code or having to maintain multiple tests.
📄️ Remotely trigger a run
Collection runs can be triggered remotely by executing a HTTP request to the collection's trigger URL. This mechanism allows integrating into your CI/CD system so tests can be executed on a newly deployed build. A typical use case would be to create a Collection which includes all the sanity tests for your environment. These tests can be executed at regular interval or you can execute all the tests on-demand when a new build is deployed.