Struggling on what to write more for acceptance tests of user stories, use cases as well

Question

I am not exactly clear on what an acceptance test is, is it basically information about the feature?

Answer 1

Ask the Product Owner "How are you going to test that this is good enough to deploy?" Everything they tell you is part of your battery of acceptance tests.

Answer 2

A User Story will typically have a number of Acceptance Criteria. They are typically written in an "As a [Role] I want [Feature] so that [Benefit]". Writing them in this way conveys good contextual information to the development team (what they need to do, why they need to do it, and who the user is).

An Acceptance test will verify one of the acceptance criteria on a User Story. Your Product Owner will write the Acceptance criteria, and ideally collaborate with you as much as possible to get them running technically in Spec Flow, Fitnesse, Cucumber etc...