New technology, new tools ...
new automation strategies?

Automation is one component of better squad performance. Automating insistent manual tasks yield team members time to solve other problems and get up with innovations that assist the job. Automated regression tests give squad fast feedback and let them add new capabilities to their product without fear of breaking anything.

Back in the 90s we had vestigial automated examination tools and dreamed of large answer, tools that not alone test system doings, but too:

• Alert us to visual differences in the UI, netmail, PDF files
• Identifies crack in our test reportage
• Tests through AND behind the UI
• Tests execution with the same test scripts (this actually did subsist back then, and was assuredness)
• Looks at our code and automatically generates regression tests (really, this exist for unit level tests back then, which is an anti-pattern)
• Let us screen email, documents, and other artifacts in addition to the UI pages & nbsp;

As we approach 2020, we see high-performing teams who can release worthful features to customers continually, with low modification failure rate and a little clip to restore service. There are many component that allow team to achieve this level. Test mechanization is entirely one of them, but it is an important one. Time that used to be spent doing manual fixation tests can be consecrate to more valuable activeness such as explorative testing. Shorter feedback cycles facilitate teams adopting continuous delivery or deployment.

Test automation is hard

Though they see the advantages of automatise regression tests, many organizations even struggle with it. If there is any test automation, it ’ s oft the province of QA/test squad members who have no coding or automation experience but are assay to automate test through the UI. The resulting unreliable and hard-to-maintain automation tests may cost the team even more time and energy than if they tested manually. & nbsp; & nbsp;

An organization may have a team of experient and competent exam automators, but they lack control over their surroundings. Developers on a separate team may be unwilling to instrument code to make it easier to test. They may be turning release feature toggles on and off without warning. A content squad may be putting new elements into the UI unexpectedly. & nbsp; & nbsp;

Consider how machine-controlled tests have typically been written. If the team designs the scheme for tryout automation, then there are well-documented landmarks to detect elements or well-defined convention for the construction and use of landmark, thing like data-attributes, element IDs, or class appellative conventions. More commonly, it ’ s up to the trial generator to figure out the right incantation of XPath expressions or CSS selectors. This can be time devour for entire pages and applications, which slows down test creation.

It also leads to automated tests and test automation frameworks only using one or two characteristics of an element to find it. If those few locators alter, the test will break even if other useful characteristics of the constituent remain the same and the overall functionality, behavior, pattern, and execution of the application are right. Fixing these then demand depart back to the original process of inspecting the page to find the correct landmarks to repair the test. The maintenance cost for bespoke machine-controlled examination can add up.

People on these teams want to amend, but they ’ re too busy attempt to keep up with manual fixation prove to experiment with changes. How can they hope to get fast, authentic feedback on the latest changes to the code understructure? & nbsp;

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

Helping teams meliorate

We ’ ve been waiting a long time for our flying cars, but the technology that can provide the test mechanization features name at the start of this articlehas started to be put to use.With cloud base, big data and the ability to treat it affordably, artificial intelligence and machine learning, we can progresstools that let people with a wide range of skillscreate utilitarian, reliable, maintainable automated tests. & nbsp;

What may be more crucial; non-coders on the squad can use these instrument efficaciously. Developers are also comfortable with these tool and can add more capabilities to the tests if postulate. A lone tester who ’ s unfortunately isolated from developers can get benefit, and the unharmed squad working together can get lots more.

The new breed of testing creature effortlesslycaptures legion characteristic of each interaction.Sophisticated algorithms may use all of those attributes to find the element, triangulate it from many slant. When the coating modification, they are even able to encounter the ingredient because they trust on more than just the one or two things that change. And at that point, if the test nevertheless passes, they can integrate the changed attribute into the fingerprint of the element going forward. This greatly trim the maintenance burden for the automated tests. There is no rework if, for instance, your button moves, changes styling, or propose “ Click hither ” instead of “ Click me. ”

Screenshot taken from mabl 's test output, showcasing how mabl collects enough fallback attributes to find ever-changing elements.

Enabling better practices

Automating simple smoking tests through the UI can be the first measure on the route to getting the full benefits of automation. The manual trial clip saved afford suspire way to learn practices like TDD and testing at former levels such as the API. & nbsp;

Now, imagine that those passably simple smoke examination could also alert the team about unexpected ocular changes! The team can inquire whether those are intentional changes, and if so, re-baseline them. The tests also render alert for page load time anomalies, which can give former monition about performance issues. These are worthful built-in benefits.

In addition to testing UI pages, this tool from the future lets yousuch as signup confirmation emails. The visual change detection automatically kick in for these too. The capability to ascertain thecontent of PDFsthat are relate from the UI pages or attach to the emails is also available - and the visual change espial also utilise to the PDFs.

This tool we ’ ve dreamed of for so long enables full automation practices. Among them is the power touse API calls from the UI teststo set up and tear down of test data, which is a full mechanisation exercise that speeds tests and makes them more maintainable. There are many ways to benefit from API requests in the test. For example, asserting that database values tally what evidence in the UI. This gives teams options for testing more deeply than what appear in the UI itself.

As teams start automating fixation tests or seek to add to existing tryout suites, they may struggle to prioritise what tryout are needed yet. Another benefit of today ’ s technology is the ability toidentify what tests interact with each UI page.We have tools like Segment that let us capture how client interact with the UI pages in production. The power to compare this usage information with the current test reporting helps us know where to focus our automation efforts next.

A new generation of creature, new models for scheme?

If you had ask us 20 or so years ago, will there ever be a trial mechanisation puppet that can be worthful and operational by everyone on a delivery team, we ’ d have said that ’ s just wishful cerebrate. Thanks to the power togather, store, process (quickly), and use large amounts of data,tools that let you start simply but see about many scene of your product ’ s quality are here. One tryout can check a UI characteristic ’ s behavior, learn whether there are visual or performance changes, and control other artifactsuch as emails and PDFs.At the same time, it can ascertain behind the UI straight to the waiter and database via the API. Your team ’ s developer can choose to add some custom-coded trial steps. As you make your machine-controlled test suite, the instrument help you dog coverage, prioritize what to automatize next, and achieve the right balance of trial to give your squad confidence for frequent deploys to production. & nbsp;

At the like clip, cloud base now grant teams toeach in its own container, so that the feedback is only as slow as the longest test. That is a game-changer for tests through the UI, especially for squad that want to screen in multiple browsers. & nbsp;

The test automation pyramid and trigon models have guided a strategy of promote as many tryout as potential down to more grainy stage. Teams prefer tests that are nimble to indite and quick to run, and derogate the tests that are painful to preserve and slow to run. With trial that run more reliably through the UI, run faster in the cloud, and test much more than feature behavior, the new-generation tools might change the mechanisation model shape. Teams can try new strategies to successfully shorten feedback loops with automation and enable continuous delivery or deployment.