We’ve noticed that automation testing often ends up taking as much effort as development—sometimes even more—because of all the tweaks and maintenance involved.
That’s why we’re building a no-code automation testing tool designed for anyone with domain expertise—whether you’re a developer, QA, manager, or business owner—to create and manage tests without the usual complexity.
We’re still in the early stages and focused on making test maintenance simple and user-friendly. What’s the biggest challenge you face when maintaining automated tests?
Your insights could help shape a solution that truly works for the industry.
There are a lot of tools out there proposing no-code automation. For many they struggled with scaling, integration 3rd party elements and complexity.
It’s a good question, what problem are no code tools trying to solve?
What as tester or automation engineer would I learn from using such a tool, how transferable is that knowledge if I switched companies to highly coded environment.
The idea of designed for domain expertise, sort means aimed at business users to create these, could it be a waste of tester skills to be using these? Is anyone can use it a negative thing?
If anyone can use it then its likely a prime candidate for AI agents, plan, execute, self heal with simple oversight from someone. Playwright is already entering this realm even though it is coded but it has the agents doing the coding.
My challenge has always been whether or not it is finding useful things and that is usually a deeper more complex activity that requires constant learning. I am not seeing a lot on the tool front that have that as their primary goal and usage scenario even with the advancement of agents, self healing and single click solutions.
What’s the biggest challenge you face when maintaining automated tests?