testtalks.comfather Joe Colantonio, who has been an counselor-at-law and public anatomy in the mechanisation testing space for years, came out witha blog situationback in January featuring 7 predictions for how the state of automation testing would evolve in 2019. We found the fact that 6 of the predictions aligned with current aspects of mabl very encouraging, with 3 of them explicitly report, and. With this article, we ’ re going into deepness on how mabl today embodies each of these predictions and why these practices will better the QA process.

Prediction 1: Maintenance of Automated Tests Will Get Easier

Joe really gave us a shout-out in this section, linking to he did with Dan Belcher, one of our co-founders, in 2017. In the podcast, Dan point a survey mabl did of over 100 companies on the struggles prove teams face. He plant the number one struggle is the ability to create and maintain exam automation. This was before encrypt work had started on mabl, so we naturally picked alleviating the strain of test creation and upkeep as our two of our main goals. To simplify the maintenance of tryout, we decide to center on integrating auto-healing into every test, which Joe goes into more depth in with his next foretelling.

Prediction 2: Heal Thyself Automation

Joe ’ s theory about auto-healing, which is a technology that allows tests to look for a correct solution when a measure can ’ t be purpose, is that more test mechanization tools will begin using it in 2019. The biggest benefit of auto-healing in test automation is that it has the potential to remove the need for human intercession on your exam every time your application changes, which is one of the hardest hurdling to clear for test automation. Auto-healing substance that when an element in a step can ’ t be found, mabl automatically looks for any like factor to the one used in the step and, when it bump one, will complete the test using it. You can see this in the insights mabl send you: even before the insight about an auto-heal is direct to you, the test has already been run once with the auto-healed change and has surpass successfully. This means the report the tester find in the form of an insight is much more than a simple “ this examination miscarry because of a UI change ” answer; its suggested new element has led to an instant fix of the test. The coverage of these changes by testers that we described in the last subdivision are done through these easily approachable insight that you can get through Slack, email, or just through the app. This capability allows testers to eliminate much of the time they spend maintaining tests when small-scale changes to their UI occur and alternatively focus on better test coverage and exploratory testing — something machines can ’ t do.

Prediction 3: AI Test Automation Assistance

Joe ’ s next point is about these case of brainstorm, specifically how they can point out and send you to the specific errors in your test runs without you having to dig through innumerable test run logs to find them yourself. Besides insights that point you to the specific step in the test that they failed on, two of mabl ’ s more unique types of perceptiveness focus on visual and performance aspects of your covering past what the exam stairs do. As a particular test is run repeatedly, mabl progress a visual model using screenshots taken during the test and a page load time model of each page using the runtimes enter. If a journeying ’ s runtime is significantly outside the predicted range of the model, mabl will alert you to the unexpected behavior, and likewise, an alert will be sent if a optical change to the model come.

Prediction 4: Automation Tool Diversity

In this section, Joe do the interesting observance that a new crop of proprietary vendor tools are commence to be adopted by teams whose primarily testing tool has been Selenium, which had be the tool that terminate the browser-based automation tool vendors of the past. There ’ s no one magical puppet that will solve all the test mechanization trouble we ’ re facing in one fell slide, so these tools are specializing in more specific aspects of prove and using new technologies to cater to “ different teams with different needs, styles, and preferences ” as Joe puts it. Many of these tools, including mabl, apply AI and ML to enhance test stability and provide additional information from test test.

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

Prediction 5: The Return of Record and Playback Automation Tools

Joe allege that in this new crop of tool, we are seeing evolutions of the old capture/playback tools that were prone to unreliability and hard to preserve. To combat the problems those types of tests confront, the mabl trainer retains the basic functionality of check a exam by mimicking the exploiter ’ s journeying that capture and playback creature are free-base on and do incisively as Joe predicted: “ use machine learning to help improve reliability at runtime ”. Auto-healed steps battle the issue of tests failing after code changes. The test ’ s maintenance is also streamlined with a comprehensive dashboard where you can review the test output, register journey steps, and insights in plain english, as well as make edits to the journey at any time. All tests are also run in the cloud, meaning there are no concern about maintaining your base either.

Prediction 6: Continuous Testing Top Buzzword

According to Joe, the better definition of continuous examination is “ the power to instantly assess the risk of a new release or alteration before it involve customers. ” Essentially, you desire to find the glitch in your package instead than have your users discover them foremost by testing before the release locomote out, as it travel out, and while it ’ s out. This is the variety of process where mabl can really shine, with its capacity for continuous testing and. mabl ’ s own Lisa Crispin is presently writing on having your squad adopt holistic or “ displacement left / shift right ” testing throughout the unnumbered eyelet of construction, delivering and learning from new feature that constitutes continuous testing.

Thanks again toJoefor the insightful article! We be happy to be include in it and especially excited we could expand on it with our own perspective.

To test out these features of mabl yourself, or.