The mabl integration with Bitbucket Cloud allows you to easily integrate cross-browser UI testing in your Bitbucket pipeline workflows, so your team can catch and fix issues earlier in the development cycle. With mabl and Bitbucket, every team can now realize the true potential of CI/CD - innovation at speed without the disruption of production bugs.
Adding a mabl Pipe to your Bitbucket pipelines enables you to run automated mabl tests with every build. When the mabl pipe is triggered, it will create a deployment event in mabl which in turn will trigger corresponding test runs for that deployment. The pipe will wait for completion of the tests and will return
success, if all tests have passed, or
fail if any of the tests fail.
- Automatically test builds for visual, functional and performance regressions on every deployment
- Automatically decide to pass or fail a build based on the mabl test results
- Test every pull request (PR) and see results in the Code Insights report for the PR
To get started, all you need to do is add four lines of code to your
bitbucket-pipelines.yml file, with many optional variables for fine-grained control. You can find the mabl pipe under the Testing category on the Bitbucket integrations page as shown below, or go directly to the public mabl pipe repo.
After you add and run the mabl pipe, you can see the test results summary directly in your pipeline build output.
There will also be a link to the test results in mabl which contain comprehensive diagnostics data such as screenshots, DOM snapshots, network activity and more.
Behind the scenes, the mabl pipe relies on the mabl CLI to orchestrate the test runs and get the test results back to Bitbucket. You can use CLI outside of Bitbucket to create and run tests locally, including support for
headless mode, and much more.
Bitbucket Code Insights surface information relevant to a pull request, so the author and reviewers are able to make better informed decisions. Integrating mabl in your Bitbucket workflow can provide you with a quality report for every PR commit that gets deployed via Bitbucket pipelines.
Using the mabl pipe, when you open up a pull request in Bitbucket and deploy the code commit, you will automatically see mabl test results directly in the context of the PR via Bitbucket Code Insights.
Testing your pull requests with mabl helps you catch issues earlier in the development cycle, when it is easier, faster, and cheaper to fix them. Moreover, everyone reviewing the PR will have confidence that not just the code but also the user experience with the application has been tested.
Updated about 1 year ago