Update Project Management
parent
112509d161
commit
255b2b828f
1 changed files with 0 additions and 15 deletions
|
@ -113,21 +113,6 @@ Example:
|
|||
> then I am redirected to the page from which I left the comment.
|
||||
|
||||
|
||||
|
||||
We use a syntax borrowed heavily from the test framework [Behat](http://behat.org/en/latest/), a test framework, to ease the transition between development and testing.
|
||||
|
||||
For example,
|
||||
|
||||
**Staff see a registrant's course registration info.**
|
||||
|
||||
**Acceptance Criteria**
|
||||
Given that I am logged in as staff,
|
||||
when I visit at a registrant's user profile at /user/[username],
|
||||
then I see a list of all registrants from that household, including
|
||||
* DOB/age
|
||||
* emergency contact information
|
||||
so that I can best serve that registrant and understand their orders and their needs.
|
||||
|
||||
If Acceptance Criteria is undefined or is still a work in progress, we add the label ~"Needs Clarification". User stories should only be worked on when acceptance criteria has been approved by the client (ideally someone with the role in the user story).
|
||||
|
||||
We also use a **Background** section to expand on the "why" of the user story. This fuller context helps anyone working on it, design, develop and test authentically.
|
||||
|
|
Loading…
Reference in a new issue