Running tests on deployment mabl provides a variety of ways to integrate your automated end-to-end tests with your existing CI/CD pipeline include native plug-ins and a helpful curl-command builder.
For all of the following integrations, your plans must be configured to use a deployment event as a trigger.
You can use the mabl Jenkins integration plugin to automatically trigger specific environment or application plans to run as a build stage with your existing Jenkins setup. Learn more.
mabl's Bamboo integration plugin is used to automatically trigger specific environment or application plans to run as a build stage in your current Bamboo pipeline. Learn more.
With mabl you can integrate your mabl tests directly into your build and release pipelines inside Azure DevOps. Within Azure DevOps, use the mabl pipeline task to automatically trigger specific environment or application plans to run as a build task. 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 - in addition to triggering test runs - allow you to see test result summaries as well as to review test results in merge requests. Learn more.
You can 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.
The trigger-tests Orb can be added to CircleCI pipelines to automatically trigger plans to run based on a wide variety of options. Learn more.
You can easily integrate mabl with most other CI/CD solutions through our built-in curl command builder. Learn more about integrating this way.
Updated over 1 year ago