Scriptless automation is growing

Scriptless automation tools - PART 1

I wrote a first article on scriptless automation tools. In it, I talked about tools with two distinct objectives:

This means that these tools are designed to be used and mastered by anyone working in IT, even by people with little or no technical knowledge. This could be business profiles or testers who don't know the code but are highly skilled in their ability to design tests. Tools based on this objective have generally done a great deal of work on ergonomics and test display. This also concerns the selection of identifiers, with capture tools that are often visual and hide the technical part.

This means using a single tool (and therefore mastering a single tool) to automate a large number of software applications or parts of them. Examples include APIs, web GUIs, desktop or mobile applications, etc. Tools based on this objective have benefited from a great deal of work on the architecture of their software. This provides a technical overlay. But this overlay can then be adapted to different technologies.

Scriptless automation tools - PART 2

Following issue 15 of Quality Matters, I wrote a second article of the same name, which appeared in issue 16.

In fact, since 2020, the major software testing publishers have turned the corner on no-scripting, using the power of AI. We can consider these publishers' tools (at least for Eggplant and UFT One) as the "2nd generation" of no-scripting automation tools, as they take the concept of "being able to automate all technologies with the same tool" a step further by offering a single test capable of running on different environments such as a computer (different browsers) and a phone (Apple or Android).

This change explains why we are currently seeing the emergence of tools such as Tosca (Tricentis) or UFT One (Open Text).