Acceptance Criteria (Given, When, Then) is part of the following frameworks:

What ChaptGPT says about it...

Acceptance Criteria (Given, When, Then) in the context of Test Driven Development

Acceptance Criteria (Given, When, Then) in Test Driven Development

In the context of Test Driven Development (TDD), Acceptance Criteria are defined using the Given, When, Then format to describe the desired behavior of a feature or user story. This structured approach helps in ensuring that the implemented code meets the expected requirements.

Given: Describes the initial context or state of the system before the test scenario is executed.

When: Specifies the action or event that triggers the test scenario.

Then: Defines the expected outcome or result that should be observed after the action has been taken.

By breaking down the acceptance criteria into these three parts, teams can clearly define what needs to be implemented and tested in a user story. It also helps in creating automated acceptance tests that can validate whether the implemented code meets these criteria.

Resources:

  1. Agile Alliance - Acceptance Criteria
  2. Atlassian - Given-When-Then
  3. SmartBear - Acceptance Criteria

Google Links

Except where otherwise noted, content on stephanhagemann.com is licensed under CC BY 4.0 by Stephan Hagemann