Atnaujinkite slapukų nuostatas

El. knyga: How Google Tests Software

3.77/5 (1734 ratings by Goodreads)
, ,
  • Formatas: 320 pages
  • Išleidimo metai: 21-Mar-2012
  • Leidėjas: Addison-Wesley Educational Publishers Inc
  • Kalba: eng
  • ISBN-13: 9780132851558
Kitos knygos pagal šią temą:
How Google Tests SoftwareDidesnis paveikslėlis
  • Formatas: 320 pages
  • Išleidimo metai: 21-Mar-2012
  • Leidėjas: Addison-Wesley Educational Publishers Inc
  • Kalba: eng
  • ISBN-13: 9780132851558
Kitos knygos pagal šią temą:

DRM apribojimai

  • Kopijuoti:

    neleidžiama

  • Spausdinti:

    neleidžiama

  • El. knygos naudojimas:

    Skaitmeninių teisių valdymas (DRM)
    Leidykla pateikė šią knygą šifruota forma, o tai reiškia, kad norint ją atrakinti ir perskaityti reikia įdiegti nemokamą programinę įrangą. Norint skaityti šią el. knygą, turite susikurti Adobe ID . Daugiau informacijos  čia. El. knygą galima atsisiųsti į 6 įrenginius (vienas vartotojas su tuo pačiu Adobe ID).

    Reikalinga programinė įranga
    Norint skaityti šią el. knygą mobiliajame įrenginyje (telefone ar planšetiniame kompiuteryje), turite įdiegti šią nemokamą programėlę: PocketBook Reader (iOS / Android)

    Norint skaityti šią el. knygą asmeniniame arba „Mac“ kompiuteryje, Jums reikalinga  Adobe Digital Editions “ (tai nemokama programa, specialiai sukurta el. knygoms. Tai nėra tas pats, kas „Adobe Reader“, kurią tikriausiai jau turite savo kompiuteryje.)

    Negalite skaityti šios el. knygos naudodami „Amazon Kindle“.

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 youre not quite Googles sizeyet!

 

Breakthrough Techniques You Can Actually Use

 

Discover 100% practical, amazingly scalable techniques for analyzing risk and planning teststhinking like real usersimplementing exploratory, black box, white box, and acceptance testinggetting usable feedbacktracking issueschoosing and creating toolstesting Docs & Mocks, interfaces, classes, modules, libraries, binaries, services, and infrastructurereviewing code and refactoringusing test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an acceleratorand make your whole organization more productive!

 
Foreword xiii
Alberto Savoia
Foreword xvii
Patrick Copeland
Preface xxiii
Chapter 1 Introduction to Google Software Testing
1(14)
Quality≠Test
5(1)
Roles
6(2)
Organizational Structure
8(2)
Crawl, Walk, Run
10(2)
Types of Tests
12(3)
Chapter 2 The Software Engineer in Test
15(60)
The Life of an SET
17(35)
Development and Test Workflow
17(5)
Who Are These SETs Anyway?
22(1)
The Early Phase of a Project
22(2)
Team Structure
24(1)
Design Docs
25(2)
Interfaces and Protocols
27(1)
Automation Planning
28(1)
Testability
29(3)
SET Workflow: An Example
32(8)
Test Execution
40(1)
Test Size Definitions
41(3)
Use of Test Sizes in Shared Infrastructure
44(2)
Benefits of Test Sizes
46(2)
Test Runtime Requirements
48(4)
Case 1 Change in Common Library
52(2)
Test Certified
54(8)
An Interview with the Founders of the Test Certified Program
57(5)
Interviewing SETs
62(6)
An Interview with Tool Developer Ted Mao
68(2)
An Interview with Web Driver Creator Simon Stewart
70(5)
Chapter 3 The Test Engineer
75(112)
A User-Facing Test Role
75(1)
The Life of a TE
76(99)
Test Planning
79(18)
Risk
97(11)
Life of a Test Case
108(5)
Life of a Bug
113(14)
Recruiting TEs
127(7)
Test Leadership at Google
134(3)
Maintenance Mode Testing
137(4)
Quality Bots Experiment
141(12)
BITE Experiment
153(10)
Google Test Analytics
163(6)
Free Testing Workflow
169(4)
External Vendors
173(2)
An Interview with Google Docs TE Lindsay Webster
175(6)
An Interview with YouTube TE Apple Chow
181(6)
Chapter 4 The Test Engineering Manager
187(42)
The Life of a TEM
187(2)
Getting Projects and People
189(2)
Impact
191(2)
An Interview with Gmail TEM Ankit Mehta
193(5)
An Interview with Android TEM Hung Dang
198(4)
An Interview with Chrome TEM Joel Hynoski
202(4)
The Test Engineering Director
206(1)
An Interview with Search and Geo Test Director Shelton Mar
207(4)
An Interview with Engineering Tools Director Ashish Kumar
211(3)
An Interview with Google India Test Director Sujay Sahni
214(5)
An Interview with Engineering Manager Brad Green
219(3)
An Interview with James Whittaker
222(7)
Chapter 5 Improving How Google Tests Software
229(8)
Fatal Flaws in Google's Process
229(2)
The Future of the SET
231(2)
The Future of the TE
233(1)
The Future of the Test Director and Manager
234(1)
The Future of Test Infrastructure
234(1)
In Conclusion
235(2)
Appendix A Chrome OS Test Plan
237(10)
Overview of Themes
237(1)
Risk Analysis
238(1)
Per-Build Baseline Testing
239(1)
Per-LKG Day Testing
239(1)
Per-Release Testing
239(1)
Manual Versus Automation
240(1)
Dev Versus Test Quality Focus
240(1)
Release Channels
240(1)
User Input
241(1)
Test Case Repositories
241(1)
Test Dashboarding
241(1)
Virtualization
241(1)
Performance
242(1)
Stress, Long-Running, and Stability
242(1)
Test Execution Framework (Autotest)
242(1)
OEMs
242(1)
Hardware Lab
242(1)
E2E Farm Automation
243(1)
Testing the Browser AppManager
243(1)
Browser Testability
243(1)
Hardware
244(1)
Timeline
244(2)
Primary Test Drivers
246(1)
Relevant Documents
246(1)
Appendix B Test Tours for Chrome
247(6)
The Shopping Tour
247(1)
The Student Tour
248(1)
Suggested Areas to Test
248(1)
The International Calling Tour
249(1)
Suggested Areas to Test
249(1)
The Landmark Tour
249(1)
Suggested Landmarks in Chrome
249(1)
The All Nighter Tour
250(1)
Suggested Areas to Test
250(1)
The Artisan's Tour
251(1)
Tools in Chrome
251(1)
The Bad Neighborhood Tour
251(1)
Bad Neighborhoods in Chrome OS
251(1)
The Personalization Tour
252(1)
Ways to Customize Chrome
252(1)
Appendix C Blog Posts on Tools and Code
253(12)
Take a BITE out of Bugs and Redundant Labor
253(2)
Unleash the QualityBots
255(2)
RPF: Google's Record Playback Framework
257(3)
Google Test Analytics---Now in Open Source
260(5)
Comprehensive
260(1)
Quick
260(1)
Actionable
260(1)
Sustained Value
260(5)
Index 265
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."
Daugiau apie elektronines knygas Daugiau apie elektronines knygas
Pastovi nuoroda: https://www.kriso.lt/db/97801328515586e.html
Raktažodžiai: