Dec 14, 2017
Ken Pugh, author of "Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration", gives us a lesson on Acceptance Test-Driven Development (ATDD) and Behavior-Driven Development (BDD). And guess what? They aren't as different as you may think. It comes down to whether the tests are written based on acceptance criteria or on the behavior that a system must meet. Pugh reminds us that the important thing is getting the customer representative, the developers and the testers together to write the acceptance criteria in plain human language before a line of code is even written. More kernels of wisdom from Pugh:- "Fixing a defect is valuable, but preventing a defect is even more valuable."- If during development you can't ship until a particular test passes, then that test is a requirement. "Testers aren't writing tests, they're writing requirements."- "If you take more than half an hour to write the tests, then your story is probably too big."- "If you feel like you need a defect tracking system... you've got too many defects. I have been in places where they actually have just one defect! "
Howard Sublett hosts at Southern Fried Agile 2017 in Charlotte, North Carolina.
To receive real-time updates: Podcast library: www.agileamped.com Subscribe to our newsletter: www.solutionsiq.com/agile-amped/ Connect on Twitter: twitter.com/AgileAmpedFollow us on Facebook: www.facebook.com/agileamped