Improving your Test Driven Development

Conference

DevOps, Agile, Methodology & Culture

I’ve been using TDD/BDD at work for the last 13 years, I also teach and mentor teams on this subject. I’ve found that misconceptions and errors in this field are shared, and that most of us make the same mistakes. Give me 45 minutes of your time, and I’ll try to address the most common problems, hoping to improve your TDD/BDD situation as much as possible. I’ll show you how to solve miscommunication and lost art of requirement gathering, by focusing on readability, introducing just enough of Domain Specific Language, and sorting out what is important and what isn’t with the power of Spock. If you are not using TDD/BDD, this might also interest you - you’ll know how to start the right way.

Jakub Nabrdalik
Solution architect with 16 years of hands-on commercial experience including microservices, azure, java/c#/groovy/kotlin, managing an IT branch and leading teams. Teaching architecture, Domain Driven Design, distributed systems, Test and Behavior Driven Development, Spring for the last 10 years. More than 60 talks, 200 workshops, and a lot of long running systems on production. Ex WJUG, WGUG, Spring Lans leader, in Devoxx PL programme committee responsible for Architecture path.

Jakub Nabrdalik

Solution architect with 16 years of hands-on commercial experience including microservices, azure, java/c#/groovy/kotlin, managing an IT branch and leading teams. Teaching architecture, Domain Driven Design, distributed systems, Test and Behavior Driven Development, Spring for the last 10 years. More than 60 talks, 200 workshops, and a lot of long running systems on production. Ex WJUG, WGUG, Spring Lans leader, in Devoxx PL programme committee responsible for Architecture path.