For this blog post, we guide brainchild from Angie Jones ’ sgreat post at TechBeacon.

What 's wrong with disk and playback instrument?

We ’ ve heard the reserve people in the quiz community have with record and playback tools as a result of problems they ’ ve had in the yesteryear and continue to have today. With mabl, we ’ re working to get the creation of your exam free from those job to make them as comprehensive and easily maintainable as potential. So we 're aimed at endue testers who feel left behind by the programming that test mechanization instrument like Selenium require and require easy-to-maintain and effective tests.

First trouble: Applications change oftentimes and quiz not accommodate

One of the most common trouble that hamper record and playback tools is that new development practices like DevOps and Continuous Delivery mean application changes are being pushed more frequently than ever, requiring tests to be constantly update. With this in mind, we ’ ve focused on building an auto-healing characteristic that locates changed elements when your app is update. When you firstly indite your test and interact with an element, mabl will save a number of other identifiers of that element along with the part of the component you ’ re interacting with. If any identifier of the element interacted with terminal up changing due to an update, mabl will search for the updated element in the next test run utilise those other identifiers.

An example of mabl 's auto-healing. The tryout dispatch successfully with mabl finding the ingredient after an update.

When the element is found this way, mabl will finish the examination using the latest element, then notify you of the changed step when the test completes. mabl will update the information set for that component for future test tally. If for any intellect mabl automobile healed the exam wrong, you can decline the alteration and train mabl to try something else for the next test run.This kind of auto-healing is particularly effective for testing apps with dynamic UIs, such as those built with React or Angular. We have a simple example of this in action.

Second trouble: Assertions are complicated and unintuitive to use

With mabl, we wanted averment steps in your tests to be as easy to utilize as potential, as they ’ re likely one of the most frequent steps you ’ ll be adding. The mabl trainer, our Chrome extension you use to discipline your tests, path all your interactions with your app as easily as give you the ability to add forward-looking steps in your tests. With the trainer, adding an affirmation is as simple as clicking on the element you desire to assert against and selecting what you require to assert.

In the mabl trainer, Add Assertions is the first button on the left along the bottom. You can see some of the types of assertions you can use in the trainer on the right.

Third problem: Editing recorded test is either hard or unacceptable

When mabl started its beta at the start of this twelvemonth, we were guilty of this trouble too. There was no way to edit your existing tryout and you had to re-record your entire journey if you wanted to make a change. However, the amount of feedback we see from users who want a bare way to change their tests made this one of our top priorities before our entire freeing.

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

You can redact any footstep in your journeying during training or after you 've salvage it.

Now, not only can you easy cut your examination after you ’ ve check them, you can useto delimit a set of stairs and get changes across many journey at once.

Flows are foreground in purpleness and can be relieve and used across other journeying.

Fourth problem: Inadequate reporting

One of the things we focused on heavily with mabl is providing across-the-board data about each test execution. Screenshots are take at every step in your test run so you can see the last state of your app when the test failed alongside mabl ’ s story on what caused it to fail.

In the journey output, you can see the results of all the steps, screenshots at each stride in the journeying, and visual modification lows are highlighted in purple and can be saved and used across other journeys.

You can see graphs of your test ’ s passing and failure in the preceding and each run ’ s test execution time. mabl also does more than telling you when a test passed or failed, providing you with insights when there are, and .

In the mabl app, you 'll observe graphs of your test run account and their respective run continuance.

Getting info about matter is easygoing with email notifications about your workspaces and Slack messages containing notifications for specific events, which you can customize to your liking.If you ’ re using or , you can convert your test output into Jira issues or regain detailed info about sets of tests through question.

mabl sends insights to your Slack account that can go direct to you or a groove for your whole team.

Fifth problem: Lacking integration with CI/CD pipelines

mabl was designed with CI/CD pipelines specifically in mind, as our whole mission was to. mabl has native integrations with Bamboo, Jenkins, and Slack, and with our deployment API, mabl tests can be spark from any CI platform. This countenance for mabl tests to be accomplish outside of the mabl app mechanically on deployment. You can too take vantage of webhooks toand keep your whole squad updated.

The desegregation page in the mabl app ..

With mabl, we ’ ve worked to overcome the brand that record and playback tools have and show how efficacious codeless testing using them can be. There ’ s still a long way to go, so we plan to keep improving mabl to speak farther concerns our users feature while supply new features that allow for more comprehensive examination. If there are early potentiality you ’ d like to see to help tester out there, don ’ t hesitate toand let us know! And of course, you can.