Embed Size (px)
DESCRIPTION
Citation preview
test documentation @ANGIESLIST7/3/2014
1.ONGOING DEVELOPMENT
ONGOING DEVELOPMENTfeature to feature
story to storybug fix to bug fix
ALL NEED TESTS
ONGOING DEVELOPMENTSMALL, TARGETED stories, bugs, tasks FOR
DEVELOPMENT
small, targeted tests
ONGOING DEVELOPMENTsmall, targeted tests +DRIVE+ development
via
ACCEPTANCE CRITERIA
2.ACCCEPTANCE CRITERIA
ACCEPTANCE CRITERIA = TESTCASESTESTCASES = ACCEPTANCE CRITERIA
ACCEPTANCE CRITERIA+natural language
+behaviors behaviors behaviors+avoid "click this", "type that"
ACCEPTANCE CRITERIAGIVEN I am an expired member
WHEN I choose to renew my membershipTHEN my membership should be active
AND I should be able to login, search, and buy
ACCEPTANCE CRITERIAAcceptance Criteria +DRIVES+ development
product validates behaviors are accuratedevelopment makes behaviors workqa validates behaviors via testing
3.PROCESS
PROCESSTHREE ownersproduct | dev | qa
write stories together
PROCESSacceptance criteria is +REQUIRED+ before development begins
PROCESSproduct
what we are building
PROCESSdev
how we are going to build it
PROCESSqa
how we are going to test ithow we know when we are done
PROCESSproduct == validate acceptance criteria is
accuratedev == make acceptance criteria work
qa == validate acceptance criteria "passes"
(TDD/BDD)
4.RELEASE & REPORTING
RELEASE & REPORTINGacceptance criteria archived in *+JIRA+
RELEASE & REPORTINGcategorized by functional area
(i.e. Join, Renewal, Search, Ecommerce, etc.)
RELEASE & REPORTINGmark execution status to provide traceability (by release)
owner: QA (with development team)
post-release checklist
END
