I wrote an article in September 2020 about scriptless automation tools. In it, I wrote about tools with 2 distinct purposes:
Be accessible to anyone
This means that these tools are designed to be used and mastered by anyone working in IT, even people with little or no technical knowledge. We can think of business profiles or testers who don’t know the code but are very competent in their ability to design tests. The tools based on this objective have generally done a lot of work on ergonomics, displaying the tests but also selecting the identifiers with capture tools that are often visual and hide the technical part.
Be able to automate all technologies with the same tool
That is to say, having a single tool (and therefore the “mastery” of a single tool) to automate a large number of software programs or parts of software programs such as APIs, web GUIs, desktop or mobile applications, etc. Tools based on this objective have worked a lot on the architecture of their software, which offers an overlay to the technique, an overlay that can then be adapted to the various technologies.