Chapter 7. Acceptance test-driven development
Traditional software development directed us to hand off a code-complete application to testers at the end of a lengthy development cycle. As our craft improved, we sought shorter development cycles, but we still handed off to testers. As we embraced Scrum, we removed the handoff by building a cross-functional Development Team able to perform all of the required activities. We’re getting better, but I contend that there is still room for improvement.
The physics of software development tells us that testers must have a stable, finished piece of software to click and poke. On the surface, this sounds like an honest appraisal. I mean, why bother wasting time testing software that isn’t code complete, ...
Get Professional Scrum Development with Microsoft® Visual Studio® 2012 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
