kaczor.info

I am glad I found it now. It goes well with previous post as a follow-up. This time Elisabeth Hendrickson tells us more in detail about her experiences and lessons learned from Agile testing on XP projects. You can avoid mistakes and learn some of the best practices by watching it. Someone said that the best wasy to learn is to learn on mistakes and preferably somebody-else's mistakes.

It's not possible not to notice transformation of speaker since 2005. Nice job Elisabeth!

Abstract that goes with it:

One of the things testers often notice about Extreme Programming (XP) is that there is no defined role for testers on the team. Yet XP teams describe themselves as “test infected.” They practice Test-Driven Development (TDD), writing executable unit tests before writing the code to be tested. Many teams practice Acceptance Test-Driven Development (ATDD), writing executable acceptance tests before implementing a feature. They use continuous integration to give them rapid feedback about the effects of changes. They practice pair programming, a technique that results in all code being peer reviewed before it’s checked in. In short, XP teams test continuously from the very first moment of any given project. You could even call them “test obsessed.” That obsession helps explain why Elisabeth Hendrickson, author of www.testobsessed.com, likes XP teams so much. Elisabeth has spent the last several years on a quest to discover how testers can contribute effectively on Extreme Programming projects. In this video of her STAREAST 2008 keynote presentation, Elisabeth shares her experiences and the lessons she's learned about how testers can play well and succeed on XP teams.