Integrating testing at every step of the DevOps pipeline assist us deliver the high-quality user experience we all strive for. We refer to this practice asDevTestOps, and in this position, I will share some betterment we ’ ve made to mabl to provide you with more control over screen your Journeys on deployment employ theDeployment Events API, which we also use as portion of our.

Having automated tests that activate on deployment aid developers to quickly corroborate that new codification didn ’ t cause any regressions as it makes its way across surroundings such as staging and production. It also gives peacefulness of mind to QA engineers, product coach, and other job stakeholders that any issues are proactively resolved and everything keep to operate as ask. Some issues may only become unmistakable in a production surround, so it ’ s outstanding when our tests can run on every deployment.

Here ’ s what ’ s new to the mabl Deployment Events API, or deployment API for short.

The ability of labels

Labels are a great way to form your mabl Journeys and Plans. For example, you can use label to distinguish Plans that run smoke tests, feature tests, antiphonal design tests, etc. The automation power of label lies in the ability to control which Plans execute in response to a deployment event by passing them as parameters to the deployment API. For example:

In this representative, merely Plans hold at least one of the “ smoke ” and “ login ” labels will be executed. An easygoing way to test what will happen on deployment is to use the curl dictation builder to call the API.

(Note: If you don ’ t see the same thing in your mabl surround as the screenshot above, this is because the above screenshot was taken from our dev environment. The Labels drop-down will make its way to production betimes next week.)

Here ’ s what the generated whorl command look like with labels:

In addition to labels, you can also use the deployment API to rebase the visual change model for the application or set a fixed baseline to compare against.

Creating a fixed visual diff baseline

There are times where you would like to review all optic changes, include dynamic substance, that experience occurred in the application UI after a given release. In such cases, you can use the deployment API to quickly create a new, fixed baseline for visual change espial by using the “ Set as rigid baseline for optic change models ” toggle in the curl bid builder.

Note that in this case, you shouldn ’ t toggle “ Rebaseline optic modification framework ” which will cause mabl to part rebuilding its optical models accounting for dynamical contented region and you will see results after respective journey runs.

You can use the resulting curl command to trigger a new journeying run for all Plans matching the command. This will capture new UI screenshots that will serve as a fixed baseline for optic comparability of subsequent journeying runs. In that instance, mabl will use the rigid baseline to highlight all visual diffs, include dynamic content areas, and present them to you for reappraisal. Thus, you can make sure that all visual changes are intentional and promptly identify anything that require repair.

To learn more about the deployment API, check out theand the undermentioned on-demand webinar. You can find the accompanying & nbsp;on SlideShare.