Acceptance criteria define the conditions a user story or other requirement must satisfy before it is considered complete. Developers agree them with stakeholders, then use them to guide implementation and verify that the original requirement is fulfilled. section 2.1.1 section 1.2
Effective acceptance criteria:
- Describe specific, detailed behavior rather than a high-level feature or use case. section 2.3
- Use executable scenarios, commonly structured as Given initial context, When an event occurs, Then expected outcomes follow. section 2.1.1
- Become the basis for automated tests run during acceptance and support the inner-loop code, run, test, and debug workflow. section 2.1.1 section 2.3
Appointment category selection
For the Appointments service: Given the patient has selected Cardiology, when the patient views booking options, then the application should show only options for that appointment category. This scenario provides a concrete completion check for the feature. section 2.3
Scenario: Appointment for Cardiology Given the patient has selected the Cardiology category When the patient views the appointment booking options Then the patient should only see the options for the selected appointment category.
Browse the complete Given–When–Then scenario for the appointment-category example. section 2.1.1








