Table of Contents
What Does Trigger Mean?
A trigger is an initiating event or condition that automatically starts a process, task, or workflow. In testing, triggers determine when and how tests are executed—whether on a code commit, pull request, deployment, or at a scheduled time. Triggers help automate testing and ensure it happens consistently without manual intervention.
Why Triggers Matter
Triggers are the foundation of continuous testing and automation. They enable seamless integration between development, CI/CD pipelines, and testing systems by:
- Automatically running tests at key points in the development lifecycle.
- Reducing manual effort and human error.
- Ensuring faster feedback loops after code changes.
- Maintaining continuous validation across environments.
- Allowing teams to detect regressions or failures early in the release process.
With reliable triggers, teams can align testing cadence with development velocity and deployment frequency.
How Triggers Work with Testkube
- CI/CD Integrations: Tests can be triggered automatically from tools like GitHub Actions, GitLab CI, or Jenkins after code merges or builds.
- Webhooks: External systems can send HTTP requests to trigger specific tests, workflows, or test suites in Testkube.
- API Calls: Developers and automation scripts can trigger executions via the Testkube API or CLI.
- Scheduled Triggers: Testkube supports cron-like scheduling to run tests on recurring intervals.
- GitOps Workflows: When new commits or configuration changes are detected in Git repositories, Testkube can trigger test runs automatically.