Experimenting with QA Mode
QA Mode is a stricter way to run tests with the Quash engine. While the default agent is built to understand intent and complete tasks even if the prompt isn’t perfect, QA Mode removes that flexibility. When enabled, the agent follows your instructions exactly as written with no assumptions or alternate paths. Even small deviations cause the test to fail.
This mode is designed for testers who need full control over steps, validations, and edge-case behavior.
How QA Mode Works
QA Mode follows the same three stages as every QA workflow: Planning, Execution, and Reporting but the behavior in each stage becomes stricter.
In QA Mode, prompts turn into structured test steps. Your prompts must describe:
The action
The exact condition being tested
The expected outcome
Example difference:
Regular Mode
QA Mode
“add a pizza to cart”
“search for pizza, validate results are correct, tap on the second option and add on the add to cart button."
The system uses this added clarity to test edge cases and negative scenarios, the situations where products usually break.
Once the test starts, Mahoraga switches into strict mode:
It executes exactly what you wrote
It does not reinterpret or choose alternate paths
Even small mismatches between the expectation and the UI cause a failure
This strictness is intentional. It lets teams test narrow flows that require precise control, like:
Boundary value inputs
Invalid forms
Wrong credentials
Unexpected screen transitions
Broken states in onboarding or checkout
If something doesn’t match the steps, it fails immediately giving you a clear signal instead of a silent skip.
Every QA Mode test generates a detailed report that includes:
Full step-by-step logs
Exact failure reasons
AI insights explaining what broke and why
Because QA Mode is strict, failure data becomes more reliable. You know exactly which condition failed and under what circumstance.
How to Enable QA Mode
You can turn on QA Mode while creating a new task.
Open New Task from the sidebar.
Write your test scenario the way QA Mode expects it with clear steps, defined inputs, and the exact outcome you want the agent to verify.
In the configuration panel below the prompt box, switch QA Mode ON (bug icon). It sits alongside the other controls like Vision, Reasoning, and Temperature.
Set anything else you need: device type, number of steps, time limits.
Run the task.
Once QA Mode is enabled, the agent follows your instructions word for word, and any mismatch will surface as a failure.
Example Prompts for QA Mode
“Open the Zomato app. Tap profile icon. Tap Your Orders. Validate presence of Reorder button on latest order.”
“Select the Happy Birthday gift card and tap on Buy Now. Select the amount as Rs 2000. Enter name as Kevin, input phone number as 8379796983 and email as kevin@gmail.com. Tap on the preview button and validate that the Happy birthday gift card is visible with the details we just filled.”
“Go to the Amount field. Enter “1000000”. Tap Submit. Verify that an error message appears saying the amount exceeds the limit.”
Last updated