1. test documentation @ANGIESLIST
7/3/2014

2. 1.ONGOING DEVELOPMENT

3. ONGOING DEVELOPMENT
feature to feature
story to story
bug fix to bug fix
ALL NEED TESTS

4. ONGOING DEVELOPMENT
SMALL, TARGETED stories, bugs, tasks FOR
DEVELOPMENT
small, targeted tests

5. ONGOING DEVELOPMENT
small, targeted tests +DRIVE+ development
via
ACCEPTANCE CRITERIA

6. 2.ACCCEPTANCE CRITERIA

7. ACCEPTANCE CRITERIA = TESTCASES
TESTCASES = ACCEPTANCE CRITERIA

8. ACCEPTANCE CRITERIA
+natural language
+behaviors behaviors behaviors
+avoid "click this", "type that"

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. ACCEPTANCE CRITERIA
Acceptance Criteria +DRIVES+ development
product validates behaviors are accurate
development makes behaviors work
qa validates behaviors via testing

11. 3.PROCESS

12. PROCESS
THREE owners
product | dev | qa
write stories together

13. PROCESS
acceptance criteria is +REQUIRED+ before development begins

14. PROCESS
product
what we are building

15. PROCESS
dev
how we are going to build it

16. PROCESS
qa
how we are going to test it
how we know when we are done

17. PROCESS
product == validate acceptance criteria is
accurate
dev == make acceptance criteria work
qa == validate acceptance criteria "passes"
(TDD/BDD)

18. 4.RELEASE &
REPORTING

19. RELEASE & REPORTING
acceptance criteria archived in *+JIRA+

20. RELEASE & REPORTING
categorized by functional area
(i.e. Join, Renewal, Search, Ecommerce, etc.)

21. RELEASE & REPORTING
mark execution status to provide traceability (by release)
owner: QA (with development team)
post-release checklist

22. ANGIE'S LIST
Jeff Rogers
@jrojers
jrojers@gmail.com

23. END