TDD for Testers – The Star Wars Experience
Any agile methodology today will tell you that you have to use TDD to support it. But as it’s considered a developer’s job, many people with other roles don’t get into it. Which is a shame.
TDD is a great tool, not just for creating a better design. From my experience, people outside programming that paired with developers came out with a better understanding of development. The communication level between the team members sky rocketed, and of course, quality benefited – both in terms of early success in finding bugs and implementing features correctly.
In this workshop, we’ll do some mob programming. We’ll write together as a group tests and code for solving a real Star Wars problem. And we’ll discuss what we’re doing, refine our specs, as well as see what changes in the design tell us.
No need to know how to code. Star Wars knowledge is preferable. The key thing is to understand better what the other side lives. Neither of us is on the Dark Side. May the Force be with us!
Testers can give quality a boost by encouraging developers to do TDD. In order to do that, they need to understand it.
- TDD is important to testers, not just developers Developers and testers can pair on TDD Understanding TDD parts can help not only quality, but reduce maintenance costs Testing strategy should take into account TDD
- test process improvement