Acceptance criteria, tests and checklists (BDD and TDD)

Watch

You will be able to

• Write acceptance criteria as Given, When, Then
• Write the tests before the build starts
• Use a checklist inside a story instead of sub-tasks

Step by step

1. Write the scenarios Story › Acceptance criteria
   With users, at Backlog Refinement: Given the situation, When the action, Then the result. A story needs at least one before it can go into a sprint.
2. Take them to a BDD tool Acceptance criteria › Copy as Gherkin
   The scenarios come out as Gherkin, ready for a behaviour-driven test tool.
3. Write the tests first Story › Test criteria
   Unit, integration, regression, safety and compliance, and user acceptance tests, written before the build starts. DelPulse shows whether the tests came first.
4. Checklist, not sub-tasks Story › Checklist
   The steps inside the story. DelPulse does not go below the story; Jira sub-tasks come in as checklist items.
5. Done means done Story › Status › Done
   Done needs every acceptance criterion passed, every test passing and the checklist complete. DelPulse says what is missing.

Try it yourself

Practise as Omar Haddad in the demo.
View as Omar Haddad. Open “Map procedures to the discharge summary”. Were its tests written first, and what still stands between it and Done?

Open the demo as Omar Haddad Password pulse-demo-2026. The demo resets every night.

The examples use a made-up healthcare organisation. DelPulse is not only for healthcare: it can be set up for any industry, with your own names for every portfolio, programme, product and team.

Part of

Delivery team members · Product Managers and Product Owners