Documentation Index
Fetch the complete documentation index at: https://quashbugs.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Download: How to Prompt Guide (May 2026) (PDF)
Browse all prompting guides
The difference matters. Recipe prompts are about describing what to test. Task prompts are about describing what to do. The more precisely you write a task prompt, the more consistently Mahoraga executes it.
Start with shared fundamentals
Apply the shared fundamentals from Overview first: name exact UI targets, define expected outcomes, handle interruptions, and keep scope focused.
The structure that works
Every good task prompt follows the same shape:
Open the app, navigate to [screen], do [action], and verify [expected outcome].
Examples
Simple verification:
Open the app, go to the login screen, enter a valid email and password,
tap Sign In, and verify the home dashboard loads.
Navigate to the profile screen, tap Edit, change the display name to
"Test User", tap Save, and verify the new name appears on the profile page.
Add three items to the cart, apply the promo code SAVE20, proceed to
checkout, and verify the discount is reflected in the order summary.
Open the app, go to the login screen, enter a valid email with an incorrect
password, tap Sign In, and verify the error message "Incorrect password.
Try again." appears below the password field and the user remains on the
login screen.
Open the app after a fresh install. If a notification permission dialog
appears, tap Allow. If an onboarding carousel appears, swipe through all
screens and tap Get Started. Verify the home feed loads with content.
Execution-specific guidance
1. Use credentials from Apps
If credentials are configured in Apps → Credentials, reference them by name instead of hardcoding login details:
Log in using the Standard User credentials and verify the home dashboard loads.
Log in using the Admin Account credentials and navigate to the User Management panel.
2. Be explicit about navigation
Do not assume Mahoraga knows the fastest path between screens. Describe the navigation steps if the route matters for the test:
From the home screen, tap the hamburger menu, tap Settings, tap Account,
and tap Change Password.
Navigate to the Change Password screen.
Using test data with /slug
If the same task needs to run with different inputs — different user accounts, different search terms, different product selections — use Test Data instead of writing separate tasks.
Type / in the task prompt input. A dropdown appears listing available datasets with their slugs and sizes. Select one and the slug is inserted at the cursor.
When the task runs, Mahoraga executes it once per row in the dataset automatically.
Example:
Open the app and log in using /login-credentials.
Navigate to the checkout flow and complete a purchase.
Verify the confirmation screen shows the correct order details.
/login-credentials has five rows, the task runs five times — once per set of credentials.
→ Test Data
For failure patterns and corrective rewrites, see Troubleshooting Prompts.
When to use tasks vs. Test Studio
| Situation | Use |
|---|
| Quick sanity check before a release | Task |
| Verifying a specific bug fix | Task |
| Exploring a new flow you haven’t tested before | Task |
| Reproducing an issue a teammate reported | Task |
| Generating comprehensive coverage for a feature | Test Studio |
| Creating reusable tests for regression | Test Studio → save to library |
| Building tests from a PRD or Figma design | Test Studio |
| Creating tests for a sprint’s worth of tickets | Test Studio |
