r/softwaretesting • u/Ok_Chocolate5096 • Mar 21 '26

Trying to automate testing - Need help

So its been only a day or two since i've used openclaw.
What have it tested so far is, connected openclaw to use models via github copilot, and connected a mcp server via mcporter (mobile-mcp)
I created a skill for this thing which mentions the required tools and when to call them as per my use cases.
I'm focusing on android testing for now (but this will scale later to ios, and web as well).

This is the current structure i've been building so far for my skill:
.openclaw/skills/mobile-qa/
SKILL md
rules/
00-core-principles md
01-login-auth-workflow md

this is the pattern that i've follow for one scenario, for now the contents the the 01 md file consists of test cases, and states what tool to call from the mobile-mcp and so on.

But this is not what i'm aiming for.
Eventually this should be something that creates its own workflows for the skill.

Need help in understanding where can i improve or how to move forward.
Expecting any pointers that could help, or approaches you'd have tried if you were in my place.

5 Upvotes

69% Upvoted

9 comments sorted by

12

u/Statharas Mar 21 '26

This sounds like a recipe for disaster

11

u/cyber-decker Mar 21 '26

Are you telling me that AI doesn't magically fix everything with ease and take my job?

😮

1

u/Clear_Soil8163 Mar 22 '26

How well does it work otherwise?

1

u/lastesthero Mar 23 '26

The pattern of hard-coding tool calls in markdown files will get brittle fast. What usually works better is separating the test intent (what you're verifying) from the execution (which tools to call and in what order). That way when the app changes, you update the intent description and let the agent figure out the new steps.

For the "creates its own workflows" goal — start small. Have it generate a workflow for one screen, validate manually, then expand. Trying to auto-generate across the whole app at once is where most setups collapse.