Google software test path PDF download

Google, a leading generation of cool star enterprises, has launched many successful and outstanding products, not to mention search engines, such as Gmail, chrome, Google doc, G +, etc, we have also launched many short-lived products, such as Google wave.


As an enterprise that often needs to launch new products, but needs to make further choices based on user feedback, as a star enterprise that needs to make the products stable and robust to maintain customer satisfaction, how to test is a big problem. Google's experience is worth learning.

The author of this book is Google's senior ctor (if I remember correctly). He has a wealth of experience in the testing field and is familiar with Google's testing process and culture. This book introduces a wide range of details. In order not to be spoiler, I just want to give it a rough picture. Let's take a look at it for yourself. This section describes the division of Google's responsibilities, the responsibilities of developers and testers (and even happily introduces how to interview each role), and the career development path of each role; this section describes various environments for Google internal system development, how code is developed from the development environment to the production environment, and focuses on the work of different types of testers, such as how to think about it, how to Write test case (Google has its own methodology template), how to communicate with others, when to intervene in the project, how to perform the test, and how detailed the test is.


Haha .. No spoiler. Let's read the book by yourself... It is worth reading !.. Although the types and positioning of different enterprise products are different, Google cannot be copied completely, but it will be somewhat enlightening!

Friends who need to learn can download PDF http://putpan.com/fs/9yi4becnsbhub82f1/ through online storage for free

Every day, Google tests and releases millions of source files and hundreds of millions of lines of code. Hundreds of millions of building actions will trigger millions of automated tests and execute them on hundreds of thousands of browser instances. How did Google test these seemingly impossible tasks?

Google Software Testing tells you from an internal perspective how this world-renowned Internet company is addressing the unique challenges of software testing in the 21st century. Google's Software Test path captures the essence of Google's testing and the essence of the most complex software in the Age of Google testing. Google software testing describes test solutions, reveals how the test architecture is designed, implemented, and run, and introduces the role of software testing engineers; explains the technical skills that technical testers should possess and describes the responsibilities of test engineers in the product life cycle; this article describes the test management and interviews with engineers who have played an important role in Google's test history or major products, this has benefited a lot for those who try to build a test process or team similar to Google.

Finally, Google software testing also introduces the author's insights on how Google testing continues to evolve, and some predictions on Google's and even the entire industry's testing direction, I believe many readers will feel the insights and even be shocked. This book serves as a guide for anyone engaged in software testing to reach their goals.

Google software testing is suitable for developers, testers, and test management personnel. It is also suitable for the learning books of students and instructors of colleges and universities, as well as the teaching materials of training schools.

James Whittaker is Google's Engineering director, responsible for testing some Google products, including chrome, maps, and Google Web apps. Before joining Google, James worked in Microsoft and was a university professor. James is well known in the Global testing field.

Jason arbon is a Google testing engineer Te and has been responsible for testing Google Desktop, chrome and Chrome OS. Jason is also the developer of a series of open-source testing tools and personalized experiments. He worked in Microsoft before joining Google.

Jeff carollo is a test and Development Engineer set of Google. He was responsible for testing Google Voice, tool box, chrome, and Chrome OS products. Jeff provides consulting services for many Google internal development teams to help improve the code quality of these teams in their early stages. Later in 2010, Jeff moved to work as a software development engineer (SE) and led the development of Google + APIs. Before joining Google, Jeff also worked in Microsoft.

Contents of Google software testing
Chapter 2 Introduction to Google software testing 1
1.1 quality not equal to Test 5
1.2 role 6
1.2.1 Software Development Engineer (SWE) 7
1.2.2 software testing and Development Engineer (SET) 7
1.2.3 Test Engineer (TE) 8
1.3 organizational structure 9
1.4 crawling, walking, and running 10
1.5 test Type 12
Chapter 5 software test and Development Engineer 15
2.1 set job 17
2.1.1 development and testing process 17
2.1.2 who is set 21
2.1.3 Early Stage 22 of the project
2.1.4 team structure 23
2.1.5 Design Document 24
2.1.6 interface and Protocol 26
2.1.7 automation Plan 27
2.1.8 testability 28
. 2.1.9 set workflow: one instance 31
2.1.10 test execution 41
2.1.11 definition of test size 42
2.1.12 use of the test scale on the shared test platform 45
2.1.13 benefits of Testing Scale 46
2.1.14 test operation requirements 48
2.2 test and certification 54
2.3 set recruitment 62
2.4 interview with tool development engineer Ted Mao 68
2.5 dialogue with Simon Stewart, Web driver creator 70
Chapter 4 Test Engineer 75
3.1 user-oriented test role 75
3.2 testing engineer's work 76
3.2.1 test plan 79
3.2.2 risk 94
3.2.3 life cycle of test cases: 104
3.2.4 bug lifecycle 109
3.2.5 te recruitment 121
3.2.6 Google testing Leadership and Management 128
3.2.7 maintenance mode testing 131
3.2.8 quality bot experiment 134
3.2.9 bite experiment 145
3.2.10 Google test analytics 154
3.2.11 zero-cost testing process 159
3.2.12 external suppliers 163
3.3 interview with Google Docs Test Engineer Lindsay Webster 165
3.4 interview with Apple Chow, YouTube testing engineer 170
Chapter 2 Test Engineering Manager 4th
4.1 work of Test Engineering Manager 177
4.2 project and personnel acquisition 179
4.3 influence 180
4.4 interview with ankit Mehta, Gmail testing Engineering Manager 182
4.5 interview with Hung Dang, Android testing Engineering Manager 188
4.6 interview with Joel hynoski, chrome testing Engineering Manager 192
4.7 testing Director 197
4.8 interview with Shelton Mar, director of search and geographic information testing 198
4.9 interview with Ashish Kumar, director of engineering tools 201
4.10 interview with sujaysahni, Google testing Director, India 205
4.11 interview with Engineering Manager Brad Green 209
4.12 James Whittaker interview 212
Chapter 2 Google software test improvement 5th
5.1 Fatal Defects in Google processes 219
5.2 future of set 221
5.3 TB in the future 222
5.4 future of Test director and manager 223
5.5 future testing infrastructure 224
5.6 conclusion 225
Appendix A Chrome OS test plan 227
A.1 test theme overview 227
A.2 risk analysis 228
A.3 baseline test 228 for each build
A.4 daily test of last known good, LKG 229
A.5 release version testing 229
A.6 manual and automated testing 229
A.7 development and testing quality concerns 230
A.8 release channel 230
A.9 user entry 230
A.10 Test Cases Library 231
A.11 test dashboard 231
A.12 virtualization 231
A.13 231 Performance
A.14 stress, long-term operation and stability tests 231
A.15 test execution framework (Autotest) 232
A.16 OEM manufacturer 232
A.17 hardware lab field 232
A.18 End-to-End test automation cluster 232
A.19 test Browser Application Manager 232
A.20 browser testability 233
A.21 234 hardware
A.22 timeline 234
A.23 main testing driving force 236
A.24 documentation 236
Appendix B Chrome's roaming test 239
B .1 shopping roaming 239
B .2 student roaming 240
B .3 international long-distance call roaming 241
B .4 landmarks roaming 241
B .5 242 roaming all night
B .6 official roaming test 243
B .7 roaming in dangerous areas 243
B .8 personalized roaming 244
Appendix C blog posts on tools and code 245
C.1 Use bite to remove bugs and redundancy 245
C.2 releases qualitybot 247
C.3 RPF: Google's recording playback framework 249
C.4 Google test analytics-Now open source 251

Qq 2057904338

Google software test path PDF download