# A Prompt For Writing Acceptance Criteria That Testers Accept

> Force the negative and edge cases; the happy path writes itself.

- **Author:** [Aroha Ngata (@aroha_ngata)](https://www.promptabide.com/aroha_ngata)
- **Published:** 2026-03-26
- **Updated:** 2026-08-22
- **Tags:** `product`, `requirements`, `qa`, `agile`
- **Views:** 13171
- **Likes:** 481

## Prompt

```
Generated acceptance criteria are all happy path. Three Given/When/Thens, all of them the successful case, none of them worth writing down.

Fix it by demanding a ratio:

"Write acceptance criteria for [feature]. Format: Given/When/Then.

At most 2 happy-path criteria. Then at least 8 covering:
- Every validation failure, individually
- Permission denied, for each role that can reach the screen
- Concurrency: the same action twice, or two users at once
- The empty state and the 'too many' state
- What happens if the downstream call times out
- What is explicitly out of scope

Mark any criterion where the correct behaviour is a product decision I still need to make."

That last line surfaces the arguments early. On the last feature it flagged four genuinely undecided behaviours that would otherwise have been decided by whoever implemented it.
```

---

Canonical HTML: https://www.promptabide.com/bides/acceptance-criteria-testers-accept-aroha-ngata-2
Agent guide: https://www.promptabide.com/llms.txt · https://www.promptabide.com/agent-instructions.md
Sitemap: https://www.promptabide.com/sitemap.xml