What AI based no-code Automation tool are you currently using?

Discussions
, ,
1

What AI based no-code Automation tool are you currently using?
What tool(s) were you using before this one?
Was the decision to adopt this tool based on your evaluation, or did your organization choose it?
What key advantages do you see with the new tool?
How do you feel now with the new AI tool.. is it solving your problem efficiently?

2

Can you elaborate on what “AI automation tool” mean in here?

Do you mean AI assistance, agentic AI that supports vibe coding or AI automation tool that requires no-code, explore systems on their own and write scenarios in plain english and run them?

3

Hey nat.. thanks for pointing out. I edited the ask

4

Hi Vignesh,

I am currently not using any AI non-code tool, however I watched some videos of one product that does it - Tester H

There are a few demo videos how agentic AI scans the site and tests it with no-code, something like this - Tester H. I didn’t dive deeper though.

We are still using code based tools like Playwright, Jest, React testing library for testing with a lot of AI assistance, agentic AI IDE (e.g. Cursor AI).

Recently I have also tried Playwright MCP that explores your site and writes tests for you following prompts in the file - Letting Playwright MCP Explore your site and Write your Tests - DEV Community

5

The answer depends on your specific requirements.
I think Endtest is a good option, it has great reviews and affordable prices (at least compared to other similar tools).

6

Can you please explain further on that tool? I’m currently on ito ai. Quite expensive but worth it + makes screenshots of the bug while other tools don’t. What are advantages of endtest over others? Really curious

7

I recently evaluated several Agentic tools, and one of the most interesting was Functionize.

8

I’m not using an AI no-code automation tool in production at the moment.

I wonder if “no-code” is becoming less important as a category now that AI makes code easier for more people to create and maintain.

For me, the more important questions are whether the tests are reviewable, deterministic, cheap to maintain, and easy to debug when they fail.

So I’m less focused on no-code vs code-based, and more focused on trust, reproducibility, and maintenance cost.

9

i use testbrick still one of the most reliable and useful to report bugs i find other tools flacky and AI tools not matured yet.

10

That’s interesting. How do you decide a failure is actually a product bug?

Is it based on stable repro steps, failed assertions, screenshots/logs, or something else?

That reviewability is the part I care about most: not just “the test failed”, but “a developer can trust this failure.”

11

Its based on Failed Assertions ,screenshots and logs

there is a shareable link that exposes the apis that failed or step that failed and a video so the developer can watch again.

I use it to write my automation and when a test that already passes starts to fail i will share it with the developer because there are useful info for the devloper to debug.

Also i use the Bug report feature where i can just record my screen and report it diff from the automation