Acceptance tests are created from user stories. The customer specifies scenarios to test when a user story has been correctly implemented. A story can have one or many acceptance tests, what ever it takes to ensure the functionality works. Acceptance tests are black box system tests. Each acceptance test represents some expected result from the system.
This instructions are inetended to give you a better scope of what a good User Story Acceptance Test could be like rather than a sole resource for the artifact of your project. You may need to tailor it and make several other changes to ensure it is a good fit for your use and project.
Title and Number: Using a few key words that fit the User Story Acceptance to be described. Description: High level overview of the User Story Acceptance capability provided. Status: The condition of the User Story Acceptance described. Workflow/Steps: The steps involved in using the system to provide the desired functionality. Expected Result: User Goal achieved. Actual Result: The actual behavior acheived by the user.