It seems the "Given..When..Then" format is the defacto standard for writing both acceptance criteria AND test scripts these days.
And it's a powerful tool if you use it well! A clean, clear, well-written requirement that uses this format acts as a bridge between product folk, developers and testers. Doing BDD well can reduce defects by 90%, give you faster, higher quality automated tests, AND speed up delivery.
But the truth is, many of us struggle with the format. Sometimes it feels like it slows us down, like it gets in the way of what we want to say or the test we want to write.
It sometimes feels like we spend more time thinking about the format than writing the acceptance criteria.
Because writing clear, expressive acceptance criteria in the Given..When..Then format is not as easy as it seems.
There's a lot more to it than meets the eye.
I want to show you some simple tricks that will make writing Given..When..Then scenarios both quick and easy.
I want to give you some key insights into this vital phase of agile software development.
Whether you are a product owner, a business analyst, a tester or a developer, you owe it to yourself to have these skills in your toolkit.
There is an art to writing great acceptance criteria, but it can be learned.
That's what this training course is all about.