Mabl provides a variety of ways to integrate your automated end-to-end tests with your existing CI/CD pipeline.
CI/CD integrations trigger a mabl deployment event, which is a parallel run of all plans in a workspace that match specified conditions, such as application, environment, and plan label. If you are unfamiliar with deployment events in mabl, you can learn more about how they work here.
For more high-level information on implementing continuous testing in a CI/CD workflow, learn more here.
Use the mabl Jenkins integration plugin to automatically trigger plans in a specific environment or application to run as a build stage with your existing Jenkins setup. Learn more.
Mabl's Bamboo integration plugin automatically triggers plans in a specific environment or application to run as a build stage in your current Bamboo pipeline. Learn more.
Within Azure DevOps, use the mabl pipeline task to automatically trigger plans in a specific environment or application as a build task in your build and release pipelines. Learn more.
Mabl integrates with GitHub through the mabl GitHub app and mabl Action. Doing so takes full advantage of GitHub Actions 2.0, automatic GitHub Issue creation, and filtering by GitHub data within mabl. Learn more.
Mabl provides GitLab pipeline images that allow you to trigger test runs, see test result summaries, and review test results in merge requests. Learn more.
Use the Run mabl tests step template in the Octopus Deploy process to automatically trigger plans to run based on application, environment, or plan label settings. Learn more.
Add the trigger-tests Orb to CircleCI pipelines to automatically trigger plans to run based on a wide variety of options. Learn more.
You can integrate mabl with most other CI/CD solutions through our built-in curl command builder. Learn more about setting up an API-based CI/CD integration here.
Updated 3 months ago