The first chapter of Google software testing introduction

1.Google ways to implement software: simple and straightforward

2. Quality is not equal to testing. When you put the development process and test together, like mixing in a blender, until you can not distinguish between each other, you get the quality.

3. Testing is an integral part of the development process, and when the development process and testing work together, that is when quality is achieved.

4. The Google team consists of Swe (software Development engineer), SET (Test development engineer), TE (test engineer).

5. At Google: for a tester, if you have been working in a product for 18 months, you will be able to voluntarily transfer to another product without any reason.

6.Google never included a lot of functionality in a product release.

7. Google will never include a large number of features in a product release, after the implementation of a basic core functionality of a product, immediately released to use, and then get real feedback from users, and then iterative development, product release Experience Canary version (daily build) development version ( Typically weekly)--beta version (basically the best version of the last one months)->beta or release version.

8. Google's test types are:

• Small test: Used to validate individual functions or standalone function modules, typically using mock and fake. Small tests are done by SWE, TE may be involved, and small tests are automated;
• Medium-sized testing: usually automated, and typically involves interaction between two or more two modules. The set will drive the implementation and operation of these tests, and SWE will be deeply involved and coded to maintain these tests. In the second chapter, it is also called "Integration test";
• Large-scale testing: using real user scenarios and real user data, large-scale testing focuses on the integration of all modules, but tends to result-driven and verifies that the software meets the needs of the end user. All three engineer roles are involved in large-scale testing, Through automated testing or search-based testing. It is also called system testing, end-to-end testing;

For all three types of tests, Google is more inclined to do automated testing, but Google also has a lot of manual testing. It is more likely to test new features, user experience, privacy, and so on.

Note: Some of the content is referenced in http://lijingshou.iteye.com/blog/2002534

The first chapter of Google software testing introduction