Skip to main content
A case is one row of the script you can run every release. Not the Tuesday result (that’s the run).

​
Fields that exist

  • title, description
  • preconditions
  • expected_outcome
  • priority: low | medium | high | critical
  • module
  • tags
  • required_persona_id
  • estimated_duration_minutes
  • status: draft | active | deprecated
  • steps: instruction, expected_result, notes, evidence_required
If a field isn’t in that list, SimpleUAT doesn’t have it. Don’t invent “automation ID” or “browser matrix” columns in docs.

​
Good

Title: Returning customer can apply a valid promo and place an order Preconditions: Staging. Account shopper@client.test. Cart has one in-stock SKU. Promo UAT10 from the client’s sandbox list. Step: Open cart to apply code to totals drop 10% to pay with sandbox Visa to order number shown. Expected outcome: Discount visible on summary and confirmation; order appears in account order list. Priority: high. Status: active. Evidence required on the confirmation step.

​
Bad (vague)

Title: Checkout Description: Make sure checkout works. Nobody can pass/fail that twice the same way. That’s a suite name, not a case.

​
Bad (complicated)

One case that covers guest, login, PayPal, Apple Pay, expired promo, tax-exempt, and mobile. That’s a project. Split. Use a pack like E-commerce Checkout if you need breadth, then delete what you won’t execute.

Write your first

Create suite + Add First Case.

Organize

Modules, tags, deprecate.