CI/CD & Webhooks

Testing belongs in your delivery pipeline, not off to the side. E2E Test Automation triggers runs and notifies external systems on events like pull requests, pushes, and test results, so your pipeline and your tests move together. You connect once and let the events do the work.

Who it’s for#

Teams who want tests to run automatically as part of their CI/CD pipeline and to keep results traceable back to the work that requested them.

What it does#

• Event webhooks — trigger tests and notify external systems on pull requests, pushes, and test results.
• API keys — give pipelines programmatic access to start runs and read results.
• Story links — keep tests traceable back to the work that requested them.

How it works#

Webhooks fire on the events you care about, so a pull request or push can kick off a run and a result can notify another system. API keys let your pipeline start runs and read results without manual steps, and story links connect each test to its originating work item.

Why it matters#

When testing is driven by pipeline events and reachable through an API, it stops being a separate manual step. Tests run when code changes, results flow back to your systems, and every run stays linked to the work behind it.