In the dramatic plays of continuous software development the tester's typically award-winning role as the underdog protagonist for quality is challenged by the preference of an audience who's applause cheers for rapid software delivery, improvement and adaptation. Our once-heroic and traditional gatekeeping practices in software testing are now likely to be perceived as unproductive, exaggerated blockers to the delivery of the system as a whole. We are suddenly the antihero of software, and to traditional testers that's a big wake-up call. One might argue that these evolutions in software testing require more technical capability, coding skills, business acumen and social perception than ever before. But more important than any other thing impacting a software tester's success is their ability to upgrade their perception of their own self-identity as testers.
We will review the significant changes in contemporary software development practices that have smashed the traditional definition of the software tester's role into bits and pieces. We will critique several of these new demands of testers and managers of quality teams, specifically the "how" and "when" for software testing and automation, the ever-changing nomenclature of our profession and the new solutions that enable testers to regain their position as a value-added asset to every IT initiative.