|
![]() |
|||
|
||||
OverviewDo you need to get it right, too? Then, learn from Google. Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering best practices you can use even if you’re not quite Google’s size…yet! Discover 100% practical, amazingly scalable techniques for analysing risk and planning tests. With these techniques, you can transform testing from a bottleneck into an accelerator - and make your whole organisation more productive! Samples Preview sample pages from How Google Tests Software > Full Product DetailsAuthor: James Whittaker , Jason Arbon , Jeff CarolloPublisher: Pearson Education (US) Imprint: Addison-Wesley Educational Publishers Inc Dimensions: Width: 17.90cm , Height: 1.80cm , Length: 23.60cm Weight: 0.460kg ISBN: 9780321803023ISBN 10: 0321803027 Pages: 320 Publication Date: 12 April 2012 Audience: Professional and scholarly , Professional & Vocational Format: Paperback Publisher's Status: Active Availability: Available To Order ![]() We have confirmation that this item is in stock with the supplier. It will be ordered in for you and dispatched immediately. Table of ContentsChapter 1: Introduction to Google Software Testing Chapter 2: The Software Engineer in Test Chapter 3: The Test Engineer Chapter 4: The Test Engineering Manager Chapter 5: Improving How Google Tests Software Test DashboardingReviewsAuthor InformationJames Whittaker 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 the world over. Jason Arbon is a test engineer at Google and has been responsible for testing Google Desktop, Chrome, and Chrome OS. He also served as development lead for an array of open-source test tools and personalisation experiments. He worked at Microsoft prior to joining Google. Jeff Carollo is a software engineer in test at Google and has been responsible for testing Google Voice, Toolbar, Chrome, and Chrome OS. He has consulted with dozens of internal Google development teams helping them improve initial code quality. He converted to a software engineer in 2010 and leads development of Google+ APIs. He also worked at Microsoft prior to joining Google. Tab Content 6Author Website:Countries AvailableAll regions |