Export or edit this event...

How, and When, to do TDD and BDD Together

308 SW 2nd Ave Fifth Floor
Portland, OR 97204, US (map)
Public WiFi

See the sign on the door, and check with the security guard in the lobby if you get lost.



For a long time, folks (Rob included) misinterpreted Behavior Driven Development (BDD) as “Test-Driven Development done right,” as Acceptance Test Driven Development (ATDD) with better tools, or as an umbrella term embracing both TDD and ATDD. So, how is BDD really done, and where does TDD fit in, if at all? It turns out that the real problem may lie in trying to pin down rigorous definitions for these terms, and trying to determine when to do which style of testing. Rob coaches teams to be prepared to use the BDD cycle and the TDD cycle when appropriate, and to be willing to move fluidly between these two intertwined cycles on a daily basis. Rob has witnessed significantly improved levels of communication, alignment, quality, and enthusiasm on teams -- and just in mere days, when BDD is embraced as the central activity of the whole team.

You’ll help explore why, when, and how to use both TDD and BDD together to build the most valuable and maintainable software possible.

Rob Myers is principle instructor and coach at Agile for All. He has over 30 years of professional experience with software development teams, and has been training and coaching organizations in Agile engineering practices since 1998. His courses blend fun, practical hands-on labs, "Training From the Back of the Room” learning techniques, and relevant first-person stories from both successful and not-so-successful Agile implementations. His clients have included many start-ups as well as Fortune 100 multinationals. Rob is currently working on his first technical book, Essential Test-Driven Development.