How Google tests software
Hundreds of millions of lines of code distributed across billions of source files. Billions of build actions prompting millions of automated tests daily. Hundreds of thousands of browser instances daily. Apps released at a continuous pace. Ladies and gents, it doesn't get more difficult than this (at least not by much).
About the Authors
James is an Engineering Director at Google and has been responsible for testing Chrome, maps, and Google web apps. He used to work for Microsoft and was a professor before that. James is one of the best known names in testing.
Jason is a Test Engineer at Google and has been test lead for Google Desktop, Chrome, and Chrome OS and development lead for an array of open source test tools. He worked at Microsoft prior to joining Google.
Jeff is a Software Engineer in Test and has focused on developer tools for code presubnnit testing. He has consulted with dozens of internal Google development teams helping them improve initial code quality. He converted to Software Engineer in 2010 and leads development of Google+ APIs.
About the Authors
James is an Engineering Director at Google and has been responsible for testing Chrome, maps, and Google web apps. He used to work for Microsoft and was a professor before that. James is one of the best known names in testing.
Jason is a Test Engineer at Google and has been test lead for Google Desktop, Chrome, and Chrome OS and development lead for an array of open source test tools. He worked at Microsoft prior to joining Google.
Jeff is a Software Engineer in Test and has focused on developer tools for code presubnnit testing. He has consulted with dozens of internal Google development teams helping them improve initial code quality. He converted to Software Engineer in 2010 and leads development of Google+ APIs.
Comments
Sign in, so you can add a comment.
No comments yet. Be the first!