Today, we 're proud to get our journeying with Atlassian by introducing mabl 's new integration with Bitbucket Pipelines.mablnow has its own Bitbucket Pipe that allow mabl and Atlassian users to quickly stand up uninterrupted, functional end-to-end testing in a CI/CD pipeline.

The advantage of this new integration are rooted in a mere reality: in order to achieve the benefits of uninterrupted delivery, you need fast, effective automated testing integrated throughout your pipeline. If your squad is deploy daily or multiple times a day and your current testing praxis occupy hours to run or require constant maintenance, your testing won ’ t be capable to keep up with the deployments. However, once CI/CD and automatize testing are tightly integrated, it enables a scalable rapid freeing cycle without sacrificing application quality. & nbsp; & nbsp;

With this integration, Atlassian and mabl users can easily switch testing further to the left and reap all the benefits of adopting DevOps. With Bitbucket Pipelines, you can ship quickly while mabl tests builds for functional, visual, and performance regressions on every deployment. This enables continuous testing and reduces the time developers spend on tedious server configuration, context switching, and bug set - multiplying the productivity of your team.

Intelligent CI/CD Pipelines

Intelligent CI/CD workflows can mechanically do informed decisions (such as promoting or demoting a build) based on item-by-item test output - decisions that once could only be done manually. The test result data is incorporated now & nbsp; back into the workflow, enable quicker, more effective grapevine management. By incorporating mabl test effect back into the Bitbucket pipeline, teams can detect regressions in every deployment, speed up MTTR (mean clip to repair), and reduce the costs of technical debt. For example, you could use mabl ’ s Pipe in concert with theOpsGenie Pipeto trigger alerting when deployment to production result in failed mabl tests.

Easy setup and configuration

The mabl Pipelines integration has the comfort of a native plugin, but with an innate power to customize more complex workflows. You can store and manage your build constellation in a individual bitbucket-pipelines.yml file and get started with solely 7 lines of code, then with alone 4 more to make a mabl pipage. There are no CI servers to set up, testing handwriting, or grids to manage. Just enable Pipelines and plug in a mabl Pipe to run mabl cross-browser tryout cortege.

Keep your work in sync

With the new mabl Pipe, you can keep your soma statuses in sync with your test executions and results. You can use the mabl CLI to question your workspace, applications, environments, and test; run smoking and regression tests on deployment; and see deployment test results - all in the same workflow.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Using a mabl Pipe with Bitbucket Pipelines

At the high stage, the workflow part when you deploy code changes to an environment using Bitbucket Pipelines. With a mabl Pipe activity configured, end-to-end tests set up in your mabl workspace will be triggered and run in analogue in the mabl examination cloud. If mabl discovers problem during the examination runs, it will send the test result back to Bitbucket Pipelines where you can opt to stop the pipeline or promote the build.

Setting up a mabl Pipe

Set up a repo that uses a Bitbucket Pipeline. In our example pipeline, our .yml configuration file contains one step (the only step) that uses a. You ’ ll need to retrieve the from your mabl workspace.

This is the pipeline yield. You can see our pipe output at the bottom right with test results from our “ Brookline Bikes ” examination plan containing 3 successful tests running on Chrome and a direct link to the mabl trial execution logs where you can view step-by-step screenshots, visual change, JavaScript errors and more.

Example test output in mabl (pictured below) contains the test suite run history.

Going into the test run history for an individual test run gives you step-by-step output including screenshots, DOM snapshot, trial runtime, network activity, as good as visual changes and JavaScript mistake, if any.

With integrated end-to-end testing in your CI/CD pipeline, finding and secure issues that can degrade UX continuously is a breeze. Try setting up your own mabl Pipes with Bitbucket Pipelines now:

Look for more exciting updates from mabl and Bitbucket at Atlassian Summit in March 2020.Register hereif you haven ’ t yet.