User Scenarios & Acceptance Tests are detailed requirements for the team to plan what they will develop. As a general rule, they should be understandable to nontechnical people in the business. Use a consistent pattern for writing the requirements to improve understanding and communication of what is needed and how it will be tested. Writing User Scenarios & Acceptance Tests distils, crystallises, and clarifies thought and helps break complex solutions into simpler parts.
The technical experts can then use the User Scenarios & Acceptance Tests to determine the best way to build what has been asked for.
As a (role) I want/need (ability/feature ) so that (benefit).
Use either of the two patterns below to describe each test.
As a (role) I will (specify the action/event ) to confirm that (Ability/feature ) does the following (expected outcome).
Given (one scenario and related conditions) when (specify the action/event ) then (expected outcome).
What must a well-formed US&AT be?
- Small (preferably less that 5 days to develop)