How Google Tests Software

Portada
Addison-Wesley, 2012 M03 21 - 320 páginas

2012 Jolt Award finalist!

Pioneering the Future of Software Test

Do 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 brand-new best practices you can use even if you’re not quite Google’s size...yet!

Breakthrough Techniques You Can Actually Use

Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests...thinking like real users...implementing exploratory, black box, white box, and acceptance testing...getting usable feedback...tracking issues...choosing and creating tools...testing “Docs & Mocks,” interfaces, classes, modules, libraries, binaries, services, and infrastructure...reviewing code and refactoring...using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator–and make your whole organization more productive!

 

Páginas seleccionadas

Contenido

Chapter 1 Introduction to Google Software Testing
1
Chapter 2 The Software Engineer in Test
15
Chapter 3 The Test Engineer
75
Chapter 4 The Test Engineering Manager
187
Chapter 5 Improving How Google Tests Software
229
Chrome OS Test Plan
237
Test Tours for Chrome
247
Blog Posts on Tools and Code
253
Index
265
Derechos de autor

Otras ediciones - Ver todas

How Google Tests Software
James A. Whittaker,Jason Arbon,Jeff Carollo
Vista previa limitada - 2012

Términos y frases comunes

actually AddUrlFrontend application attributes automated tests avaScript backend BITE bots browser bug database candidates capabilities Chrome code coverage codebase components Continuous Build core create debugging developers document early Engineering Productivity ensure exploratory testing FIGURE focus focused functionality Gmail Google Desktop Google testing Google’s GTCM hardware HGTS hiring impact important integration interview issues large tests look manual testing Microsoft open source percent perform problem product team quickly regression release risk role scenarios scripts Selenium SETs simple small tests software testing SWEs technical Test Analytics test automation Test Certified test code test engineering test execution test infrastructure test plan test team testable testers things Tour unit tests updates user scenarios user stories validation WebDriver WebKit write tests YouTube

Acerca del autor (2012)

James 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 personalization 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."

Información bibliográfica

TítuloHow Google Tests Software
AutoresJames A. Whittaker, Jason Arbon, Jeff Carollo
EditorAddison-Wesley, 2012
ISBN0132851555, 9780132851558
Largo320 páginas
  
Exportar citaBiBTeX EndNote RefMan