How to test in Google

Google programmers prefer quality to breadth of functionality.

Quality ≠ Testing

The phrase “testing does not determine quality” is already so beaten up that it simply has to be true. In any area of ​​development, from cars to software, it will not be possible to hone a product to perfection, if it is initially incorrectly designed. Ask any automaker who has ever recalled a batch of their cars, which are delayed attempts to tie the quality of the finished product. Do everything right from the very beginning, do not create yourself unnecessary difficulties. However, it just sounds simple. On the one hand, quality is not created by testing, on the other - without testing, it is impossible to make a quality product. How do you know how high-quality your product is without testing?
This puzzle is easily solved: stop looking at developing and testing separately. Testing and development go hand in hand. Write some code and test it. Then write a little more and test it again. Testing is not a separate practice, it is part of the development process itself. Quality testing alone cannot be achieved. The recipe for high quality: mix the development and testing in a blender until they become a single substance.

The publishing house " Peter " published the book " How to test in Google ." The book is published in limited edition.

')
The book describes the testing of software products in Google: how the processes are organized, how teams are organized, what techniques are used, who is responsible for quality. The principles on which testing is built at Google are applicable to projects and companies of any size. The authors of the book themselves worked on Google products, creating test tools, customizing processes and doing directly testing.



Just a few days you can buy it in electronic form at the lowest prices.

The book is available in paper form - 613 rubles.
PDF - 99 rubles
EPUB format - 99 rubles

Table of contents
Excerpt