Acceptance Criteria Definition
Acceptance criteria (AC) are the pre-defined requirements, boundary conditions, and standards that a software feature must meet to be accepted by a product owner or client. While a user story describes what the user wants to achieve, the acceptance criteria define the explicit rules of engagement, setting clear parameters for what success looks like in practice during agile testing.
Acceptance Criteria: Use Cases in Software Testing
- Removes Scope Creep and Ambiguity: Clear criteria set firm boundaries on feature scope, preventing unexpected scope creep late in the sprint.
- Aligns Team Expectations: AC ensures product managers, developers, and QA testers share an identical understanding of how the feature should behave.
- Enables Better Automated & Manual Test Planning: Testers use acceptance criteria as the direct blueprint for writing test cases and verification scripts in both manual and automated testing.
- Significantly Faster Feature Sign-off: With unambiguous pass/fail benchmarks, product owners can evaluate and accept user stories without back-and-forth debate.
How to Write Effective Acceptance Criteria
To write acceptance criteria, you’d focus on clarity, testability, and user intent. It's best to keep them concise, avoid technical jargon where possible, and ensure every criterion can be objectively tested as either a Pass or Fail.
While acceptance criteria can be written as simple rule-based bullet lists, one of the most effective methods in agile development is the scenario-based framework known as the Given-When-Then format.
Given-When-Then Format
- Given: Sets up the initial context or starting state (e.g., "Given a user is logged into their account...").
- When: Describes the specific action or event triggered by the user (e.g., "When they click the 'Delete Account' button...").
- Then: Defines the expected outcome or system response (e.g., "Then a confirmation modal should appear asking for password re-entry.").
Acceptance Criteria: Examples
Example 1: User Login Feature (Given-When-Then)
- Scenario: Successful Login with Valid Credentials
- Given the user is on the login page,
- When users enter a valid email address and correct password and click "Log In"
- Then users should be redirected to a personal dashboard, and a success notification should briefly display.
- Scenario: Unsuccessful Login with Invalid Password
- Given the user is on the login page,
- When users enter a valid email address but an incorrect password,
- Then an error message should display "Invalid email or password" and the password field should be cleared.
Example 2: E-Commerce Checkout Discount Code
- The discount input field must accept alphanumeric promo codes up to 15 characters.
- Applying a valid code must immediately recalculate and display the updated order total.
- An expired or invalid code must display the inline error: "This promo code is invalid or has expired."
- Only one promo code can be applied per order.