AI-Based Test Automation Tools

Part 4. AI and the QA Profession

Photo by Markus Winkler on Unsplash

Part 1 of this article, “The Current State of AI in Testing” can be found here

Part 2 of this article, “An Overview of AI-Based Test Tools” can be found here

Part 3 of this article, “AI Automation in the Wild,” can be found here

Codeless script generation has limits

Although the creation of tests using recording features is much easier and faster than using traditional tools, it rarely went absolutely smoothly. Sometimes I needed to re-record steps or part of the script. Sometimes I needed to manually add delays. Creating custom object names that followed a naming convention that included dates in the names was a challenging task in most cases. I believe that when QA looks at the data generated by automated tests she should be able to figure out what test created this data, when, and probably what build was used without opening logs or doing anything extra. While all the tools I tried allow you to add JavaScript code snippets, implementing this or other custom behavior means the automation is no longer codeless. Adding code adds all the disadvantages of maintaining it, including complex debugging. As we see despite all achievements in the AI industry, recording tests is still a bumpy process for complex UIs and…