# Writing testable acceptance criteria

*Business Analyst Study Guide · User Stories · Last updated October 15, 2026 · https://www.certifyforce.com/study-guide/business-analyst/user-stories/writing-testable-acceptance-criteria*

What acceptance criteria are, how to write each one as a single pass/fail statement of intent, how they differ from the team's definition of done, and how they decide whether a story is ready and whether it is accepted.

- Certification: Salesforce Business Analyst
- Exam section: User Stories
- Study guide: https://www.certifyforce.com/study-guide/business-analyst

**Official exam objective:**

> Demonstrate how to write acceptance criteria that convey the requirements and are ready for development.

## What the exam expects

- Define acceptance criteria and pick well-formed criteria for a given story.
- Rewrite criteria that are vague, bundle several outcomes, describe the UI, or belong to another persona.
- Use the if/then form and add criteria for edge and negative cases agreed with the business.
- Separate story-specific acceptance criteria from the team-wide definition of done.
- Decide when a story is ready (at least one testable criterion) and when it is accepted (criteria pass and definition of done met).

Key terms:
- **Acceptance criteria:** statements added to a story, each with a clear pass/fail result, that specify when the story is fulfilled.
- **Definition of done:** the completion standard the team agrees together and applies to its work.
- **If/then criterion:** a precondition paired with an expected result.
- **Intent vs solution:** what the user can do, not how the system is built to do it.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Definition | Statements added to a story, each with a clear pass/fail result | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Minimum per story | At least one acceptance criterion | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Each criterion | Independently testable; true or false | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Language | Simple, no ambiguity about the expected outcome | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Focus | Intent, not solution: the what, not the how | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Alternative format | If/then statements | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Who benefits | Project team (scope), delivery team, testers | [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story) |
| Definition of done | Decided together by the team | [Learn About Scrum](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-about-scrum) |
| Conditions of satisfaction | Drafted during backlog refinement | [Implement Scrum](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/implement-scrum) |

## Check yourself

- Why should a criterion describe intent rather than a button?
- When is a story ready to enter a sprint, at minimum?
- What does the if/then form pair together?
- Why is "code peer reviewed" not an acceptance criterion?

## Sources

- [Construct a User Story](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/construct-a-user-story)
- [Refresh Your User Story Skills](https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/refresh-your-user-story-skills)
- [Learn About Scrum](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-about-scrum)
- [Learn the Elements of the Scrum Workflow](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/learn-the-elements-of-the-scrum-workflow)
- [Implement Scrum](https://trailhead.salesforce.com/content/learn/modules/scrum-and-kanban-at-salesforce/implement-scrum)
- [Learn About User Stories](https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories)
- [Become A Business Analysis Detective](https://admin.salesforce.com/blog/2020/become-a-business-analysis-detective)
- [Explore Documentation Types](https://trailhead.salesforce.com/content/learn/modules/business-analyst_skills-strategies/learn-documentation-types-importance-documentation)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 20 linked practice questions, and unlimited timed mock exams are included with the Business Analyst pack (USD $19): https://www.certifyforce.com/practice-exams