Career Forums

What's the best format to use when writing Acceptance Criteria in User stories that suit both Devs and testers?

I like the classic user storie structure,

As a <User type>,
I want to <goal>,
So I can <benefit>

And as for acceptance criteria, I go with ordered lists, with sub items if needed, e.g.

1. The system should allow users to enter their flight number.
   • Users should be able to enter the flight number via a text input field.
   • The system should validate the format of the flight number.
2. The system should display the current status of the flight.
   • Status information should include departure time, gate number, and any delays.
3. The status check should be available 24/7.
4. The system should provide real-time updates.
   • Flight status should be updated at least every 10 minutes.

if you're interested in supercharging your user stories and acceptance criteria, check out userdoc.fyi - you can get done in 10 minutes what could normally take 10 days.