QA’s involvement in the software development life cycle
The team, including QAs, understands business priorities collectively. Then the team analyzes the requirements together and creates a couple of user stories. Each user story represents a unit of work and is a part of the bigger business feature, but each story also brings some value to the business.
A user story needs to be refined to have a set of acceptance criteria that decides whether the story has satisfied the expectations of stakeholders. Every acceptance criterion should be concise and testable.
The convention of acceptance criteria
An acceptance criterion can follow a popular structure of given-when-then. Given provides the initial context of the state of the system before the action is performed. When is the action performed given the context. Then is the expected outcome because of the action performed. An example of an acceptance criterion in given-when-then structure is as follows: “Given that...
