Testing: Acceptance Testing

Criteria for being 'done' with an issue

Acceptance Testing Template from Procore

When grooming an issue for acceptance testing, consider using the following template. This template is based on one provided by Procore, adapted for UCSB’s CS48:

# User Story
* Include a descriptive user story here. As an X (who) I can Y (what) so that Z (why).

# Why Are We Doing This?:

Document the reasoning behind the creation of this ticket.   Why is this important and/or needed?

# Scenario:

Provide a real use-case scenario that this ticket addresses, using specifics (e.g. specific names, values, places.)  Consider using a "persona" with a real name.

# Questions

List all questions that arise from a discussion of the user story in this section and answer them to create
the acceptance criteria below.

# Acceptance Criteria

List all acceptance Criteria in this section based on the answers to the questions 

#  Resources:

Include any designs/mocks/specs here, if applicable

# Definition of Done:

[ ]  There is a well defined use case / user story
[ ]  Customer feedback / validation has been received
[ ]  User documentation in README.md has been updated (if applicable)
[ ]  Code changes have been peer reviewed
[ ]  Code changes pass all unit tests
[ ]  Code changes pass all acceptance tests
[ ] UX / PM / QA have all been consulted on the changes
[ ]  The feature has been assessed as a candidate for automated tests
[ ]  The feature works as intended (functionality)
[ ]  The feature's performance has been assessed for improvements
[ ]  The features value proposition has been met
[ ] Clean up work has been completed

Acceptance Testing

Related topics: