Integrate your mabl tests directly into your build and release pipelines inside
Only mabl offers scriptless cross-browser testing, auto-healing tests, visual
testing, and diagnostics in one simple service. mabl helps you improve the speed
and quality of your release pipeline by allowing you to test every release, at
scale, on a single platform, with no infrastructure to manage. Learn more at
Launch mabl test runs as a build or release pipeline task
Fail the build or release based on the status of the mabl tests
Optionally continue on failure
View the mabl test statuses from the Tests tab in your Azure DevOps Pipeline
Provide additional configuration options to the task
Specify list of browsers to run against
Override starting URL
Specify one or more plan labels to trigger
Specify the test branch to use
Rebaseline visual change models
Set run as fixed baseline image for visual change models
After installing the mabl Integration from the Azure Marketplace you'll find
it listed in the tasks option when creating/editing a build or release
Simply type mabl into the search bar under tasks to see the integration
listed and click to select it
You will then see various configuration options presented. The only required
field is the mabl API key which you can find in the
mabl app by going to the Settings page and then
navigating to the APIs tab. Here you'll find your API key(s). Use the
dropdown menu to select the Deployments API builder tool and then pick either
an environment and/or an application. Note that you will need a
CI/CD Integration key to use with this task. See the
Deployments API docs
for more info.
Copy your API key and paste it into the config form for the mabl Integration.
Then find the environment and/or the application ID from the JSON under the
Deployments API builder and enter them in the config form as well.
You must specify at least one environment or one application in the config.
You can specify both as well.
There are other configuration options available when setting up your mabl