One of the aspects of software development that has grown in importance is the need for quality testing of new products as part of the overall process. James Whittaker, co-author of How Google Tests Software, discusses how his former company built a successful model based on the vital testing of its new services. He reviews how testing has grown as part of development and the different testing roles that Google used. His points clearly show how developers need to consider the importance of testing as a role for the developer.
James Whittaker is a technology executive with a career that spans academia, start-ups and top tech companies. He is known for being a creative and passionate leader and in technical contributions in testing, security and developer tools. He’s published dozens of peer reviewed papers, five books and has won best speaker awards at a number of international conferences. During his time at Google he led teams working on Chrome, Google Maps and Google+. He is currently at Microsoft reinventing the web.
Want to read more? James wrote How to Break Software, How to Break Software Security (with Hugh Thompson), and How to Break Web Software (with Mike Andrews). While at Microsoft, James transformed many of his testing ideas into tools and techniques for developers and testers, and wrote the book Exploratory Software Testing. His current book was written when he was a test engineering director at Google and is called How Google Tests Software (with Jason Arbon and Jeff Carollo).
JW On Tech (Whittaker's Blog)
This free podcast is from our Technometria with Phil Windley series.