Acceptance criteria are an essential part of the user story that define when the task is completed and what the testers should (at least) include in their testing. Unlike requirements, acceptance criteria is not a to-do list. It’s a list of conditions that must be met for the agreement to be considered finished.

Template

To write acceptance criteria use the  Given-When-Then formula as much as possible:

An example:

Examples


Criteria you should not include

We follow a pragmatic approach to acceptance criteria then therefore we do not include


Hints on what to think about

It is essential that the PM takes sufficient time to think through acceptance criteria. Some pointers:


Further reading:
https://rubygarage.org/blog/clear-acceptance-criteria-and-why-its-important
http://agileforgrowth.com/blog/acceptance-criteria-checklist/ 
https://medium.freecodecamp.org/the-acceptance-criteria-for-writing-acceptance-criteria-6eae9d497814