Over 30% of companies are using BDD these days, and the number is growing fast! And more and more teams rely on the Given..When..Then notation to write acceptance criteria, and use tools like Cucumber and SpecFlow to do test automation.
Problem is, many struggle to do it well. It's actually quite hard to write acceptance criteria that capture what the business really need, that cover all those tricky edge cases, and that are easy to test and automate later on.
But if your scenarios are poorly written, it will cost you. It makes automation harder, and leads to defects and rework that slow down delivery.
According to some studies, 70-85% of rework costs come from poorly written requirements.
The good news is, there is an art to writing effective acceptance criteria in the Given..When..Then notation, and it can be learned. And if you get it right, you can reduce defects and rework dramatically, AND make test automation a LOT easier.
That's what this course teaches you.
In this deep-dive video training, you'll learn: