{"id":14858,"date":"2022-03-21T17:44:55","date_gmt":"2022-03-21T17:44:55","guid":{"rendered":"http:\/\/abstracta.us\/blog\/?p=14858"},"modified":"2025-05-05T21:25:13","modified_gmt":"2025-05-05T21:25:13","slug":"low-code-for-test-automation","status":"publish","type":"post","link":"https:\/\/abstracta.us\/blog\/software-testing\/low-code-for-test-automation\/","title":{"rendered":"Low Code for Test Automation – state of the art"},"content":{"rendered":"\n
\"\"\/<\/figure>\n\n\n\n

We will share in this article a state of the art in the test automation<\/strong> field, specifically with the low code approach<\/strong>. We want to help you select the best tool for your context, offering a centralized place with information about the different options on the market. <\/p>\n\n\n\n

It\u2019s kind of difficult to distinguish if this is another marketing-created buzzword in the software development world. In the literature (blogs, websites, tech journals) I observe how different terms are used for the same idea, including \u201clow code\u201d, \u201cno code\u201d, \u201ccodeless\u201d, \u201cscriptless\u201d, and probably I\u2019m missing some.<\/p>\n\n\n\n

Basically, \u201clow code\u201d refers to an alternative approach to traditional software development. Instead of defining the expected behavior of the system in code, it tends to be more visual and use little or no code at all.<\/p>\n\n\n\n

As I see it, we are increasing the level of abstraction of the language we use to express to machines what to do. We started programming circuits, strings with 0\u2019s and 1\u2019s, assembler instructions, and then different languages providing more and more abstraction layers. Each layer is removing complexity, closing the gap between the human and the machine. The flip side is that the abstraction also has a cost, typically associated with performance or flexibility, but it typically makes sense to pay that cost in terms of productivity and results.<\/p>\n\n\n\n

We could say that low code is another abstraction layer on the top, and we are also seeing how we can benefit from this approach for test automation.<\/p>\n\n\n\n

Low code platforms for test automation aim to simplify the test automation with functionality that doesn\u2019t require the user to write almost any code. You will have a recorder that will let you create test cases easily, and edit them with a simple interface, without requiring coding skills.<\/p>\n\n\n\n

In the last few years, new low code solutions for test automation have been spinning up. There is an interesting cycle: more entrepreneurs are trying to build this type of tool, more investors are supporting them, the testing community adopts the tools and provides feedback. These are a few signs that it\u2019s an interesting approach for test automation to follow.
<\/p>\n\n\n\n

Today we are releasing the first draft of our research, just with the list of tools, as another step toward discovering blind spots and getting early feedback. <\/p>\n\n\n\n

The next steps are:<\/p>\n\n\n\n