Functional QA
This is the most straightforward way to use Aiqaramba. You describe the user flows that matter in your application and let agents verify they actually work. Sign up, login, checkout, form submissions, navigation, whatever your users do on a daily basis.
Because agents operate on real browsers through virtual devices, they catch the same issues a real user would encounter. Broken buttons, forms that don't submit, pages that error out, flows that dead-end. No selectors, no test scripts, just a plain language description of what should happen.
How we would set it up
The key to good functional QA is granularity. Each journey should test one specific thing. When a journey fails you want to immediately know what is broken without having to dig through a long multi-step test to find the failure point.
Think of it this way: if you have a journey called "test the entire checkout" and it fails, you know something in the checkout is broken but you don't know if it's the cart page, the payment form, the address validation, or the confirmation step. If instead you have four separate journeys, one for each step, the failed one tells you exactly where to look.
In practice this means you will end up with a lot of journeys, and that is fine. A typical application might have 20 to 50 functional QA journeys covering the important flows. Each one is short, focused, and easy to understand.
- Run them on a schedule. Set up a daily or hourly schedule depending on how often your application changes. For most teams, running all functional QA journeys once a day is a good starting point.
- One flow per journey. Resist the urge to combine multiple flows into a single journey. "Sign up and then buy something" is two tests, not one. Split them so failures are precise.
- Use natural language for steps. Write journey prompts that describe both the steps and the expected outcome, but keep the steps natural. Say "go to the forgot password page, enter the email, and submit" rather than "click button element with index 3." The agent knows how to find UI elements by their meaning.