Triggers Overview
Triggers is not enabled by default
Contact your project admin to enable this feature, or learn how to enable it yourself if you have admin access.
To access the Configs tab, you’ll need the project-view-configs permission,
which is available to users with the Config Manager role or other roles that
include this permission.
Triggers in Nexus enable you to automate your testing workflows by responding to events or schedules. They eliminate the need for manual intervention, ensuring consistent test execution and seamless integration with your development processes.
Nexus provides two categories of triggers, each serving a distinct purpose in your test automation pipeline:
Run Triggers
Run Triggers automate the execution of test plans. They initiate test runs based on specific events or time schedules, allowing you to incorporate testing into your CI/CD pipeline without manual intervention.
When to Use Run Triggers
- Automatically start tests when new code is deployed
- Schedule regular testing at specific intervals
- Trigger test execution from external systems like CI/CD pipelines or version control systems
Learn more about Run Triggers →
Action Triggers
Action Triggers automate responses when test runs complete. Unlike run triggers that start tests, action triggers activate after a test run finishes and perform outbound actions based on the test results.
When to Use Action Triggers
- Send test results to external monitoring or notification systems
- Update status dashboards with latest test outcomes
- Trigger downstream processes based on test success or failure
- Integrate test results into your broader development workflow