So your organisation is doubling down on agile processes, and you ’ ve been told that as part of the attempt, you necessitate to start automatize your tests. This makes sense, as testing automation can increase test coverage, and you can do a lot with them. For instance, you can integrate them into thecontinuous delivery pipelineand use them as an machine-driven caliber stage gate. You can hold a robust examination suite to determine the quality of each release candidate, and map regressions the more the trial suite footrace.

The problem is that you don ’ t incisively have cod experience, and you ’ re not sure where to start. A logical step forwards that many get taken is to adopt a disk and playback automated testing instrument.

The promise is great - all you need to do is step through your web app, and all your activeness will be recorded and become into a trial script for you, right? Well… it ’ s not that easygoing.

In this post we ’ ll cover:

1. The folly of most record and playback puppet
2. The almost effective scenarios to use them in in order to get an ROI
3. How next-generation disk and playback tools are fixing the problem that traditional record and playback tools have

Record and Playback: Promised Land or Oasis?

So you found the tool you want to use, and you go ham on creating tests for every individual test case that you hold documented, and oh boy! platter and playback automation tools definitely make test creation easy. The hard part now, is test maintenance. Consider how record and playback tools are capturing the activity in your trial. Most rely on element descriptors like XPATHs or CSS, like element IDs, to identify objects you ’ re taking activity on. This is fine if your web application is at a mature level where UI modification are seldom make. But if your organization is seek to embrace the fail-fast mindset of agile and DevOps, then it ’ s likely that your application is vary frequently, sometimes multiple time a day. The test script that you ’ re now left with break oftentimes, leave you with unreliable examination cortege that are hard to diagnose because the test hand are so twist from automatically generated code.

The hope of test automation slowly skid from your grasp like the soul from the husk of your body as you see that you ’ re spending more clip fixing and re-recording tests than testing. A small morbid? Maybe so, but this is the life of many who tread this road naively. The better way to use a traditional record and playback tool is to get acquainted with testing automation (platter a user stream and review the generated test handwriting), or for testing simple, little test cases that don ’ t change. Limiting traditional record and playback puppet to these two scenario will ensure that the tests stay manageable and beneficial.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Next-Generation AI-backed Record and Playback Tools

But it ’ s 2018 guys. In the age of AI and extensive automation, we canharness machine learning to build practical solutionsto overcome many problems—including the steep learning curve of automated test scripting. mabl and early“ third wave ” automation toolsemploy machine learning methodologies to screen automation, so that everyone—developers, quizzer, and even operations and support teams—can create reliable, and lively trial in a few moment.

How so?

1. Recording more than just UI locater

record and playback tools can ’ t rely on element IDs or XPATHs anymore, especially with modern AJAX apps that get dynamically loaded content which contain non-unique locators and IDs by nature. With the ontogenesis of SaaS and cloud entrepot, next-generation disc and playback tools canfor every factor in a test to make locating objects a breeze, even if one or several property have changed.

2. Updating tests automatically as your apps evolve

Next-generation record and playback tools should update tests automatically, reducing test maintenance virtually completely. Once we experience a ingathering of attributes for every element in a tryout, we canupdate our noesis about those elementat every codification release iteration. Just like how a codebase is a living, breathing organism, tests should also evolve with the application in development.

3. Using machine intelligence to track regressions

With cloud and machine erudition framework making machine intelligence and analytics so accessible, we can model characteristics of our applications through regression testing. These can run from performance anomalousness detection, to traditionally computationally intensive summons, liketracking visual alteration. Using robust analytics engines available in the cloud will let us rate the health of a release, not just free-base on test failures, but on thetrajectorycreated from our regression examination.

4. Plugging functional UI tests into your software delivery pipeline

Now that we have a good formula for a best platter and playback tool, we can plug reliable functional and UI tests. record and playback tools aren ’ t but for automating elementary test suit anymore, but they can become a legitimate benefactor in increase test coverage in the agile and DevOps age, just as you ’ ve always woolgather of.

mabl is an automated examination service that runs in the cloud, and uses machine learning to make disc and playback test automation just as described above. You can try mabl for costless atwww.mabl.com.