acceptance criteria @angieslist

533 views

Published on

Published in: Software, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
533
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

acceptance criteria @angieslist

  1. 1. test documentation @ANGIESLIST 7/3/2014
  2. 2. 1.ONGOING DEVELOPMENT
  3. 3. ONGOING DEVELOPMENT feature to feature story to story bug fix to bug fix ALL NEED TESTS
  4. 4. ONGOING DEVELOPMENT SMALL, TARGETED stories, bugs, tasks FOR DEVELOPMENT small, targeted tests
  5. 5. ONGOING DEVELOPMENT small, targeted tests +DRIVE+ development via ACCEPTANCE CRITERIA
  6. 6. 2.ACCCEPTANCE CRITERIA
  7. 7. ACCEPTANCE CRITERIA = TESTCASES TESTCASES = ACCEPTANCE CRITERIA
  8. 8. ACCEPTANCE CRITERIA +natural language +behaviors behaviors behaviors +avoid "click this", "type that"
  9. 9. ACCEPTANCE CRITERIA GIVEN I am an expired member WHEN I choose to renew my membership THEN my membership should be active AND I should be able to login, search, and buy
  10. 10. ACCEPTANCE CRITERIA Acceptance Criteria +DRIVES+ development product validates behaviors are accurate development makes behaviors work qa validates behaviors via testing
  11. 11. 3.PROCESS
  12. 12. PROCESS THREE owners product | dev | qa write stories together
  13. 13. PROCESS acceptance criteria is +REQUIRED+ before development begins
  14. 14. PROCESS product what we are building
  15. 15. PROCESS dev how we are going to build it
  16. 16. PROCESS qa how we are going to test it how we know when we are done
  17. 17. PROCESS product == validate acceptance criteria is accurate dev == make acceptance criteria work qa == validate acceptance criteria "passes" (TDD/BDD)
  18. 18. 4.RELEASE & REPORTING
  19. 19. RELEASE & REPORTING acceptance criteria archived in *+JIRA+
  20. 20. RELEASE & REPORTING categorized by functional area (i.e. Join, Renewal, Search, Ecommerce, etc.)
  21. 21. RELEASE & REPORTING mark execution status to provide traceability (by release) owner: QA (with development team) post-release checklist
  22. 22. ANGIE'S LIST Jeff Rogers @jrojers jrojers@gmail.com
  23. 23. END

×