Skip to main content

​
Where to create

  • Dashboard → Test Cases → “Add test case”
  • Provide a concise Title and detailed Instructions

​
Best practices

  • Be goal‑driven: describe the user outcome, not low‑level taps
  • Use stable identifiers: reference visible labels/placeholders, not coordinates
  • Include acceptance criteria: what success looks like
  • Provide context if needed: accounts, seed data
  • Keep steps deterministic: avoid ambiguous wording like “might”, “sometimes”

​
Perfect template

Steps:
1) [first action in natural language]
2) [second action]
Expected result:
- [what should be visible/true at the end]

​
Examples

Goal: Verify a user can sign in with valid credentials
Steps:
1) Open the app and tap "Sign In"
2) Enter email "[email protected]" and password "Password123"
3) Tap the "Continue" button
Expected result:
- A screen with the title "Home" is visible

Goal: Verify a product can be added to the cart
Steps:
1) From the home screen, open "Search" and type "AirPods"
2) Select the first product in the list
3) Tap "Add to cart"
Expected result:
- A confirmation appears and the cart badge shows 1 item