(
a) Read Google test the way I felt.
1, such a test reform must be the entire company's uniform behavior, the need for the full cooperation of various departments after a considerable period of time to complete the precipitation. To see the company's corporate culture. 2, manual testing personnel will experience testing, experience testing can only be done under the participation of people. This part of TE will be reduced, but will not disappear. 3, add set of the position is only to assist the unit Test SWE, but in accordance with the SWE conditions are not easy to find, even if found, the treatment is more than the same as SWE, testing department in a vacuum to add a high-cost position, the boss can accept? 4, the role of TE is responsible for user experience testing, automated script testing. But in an agile fast iteration, the need to improve the situation, the automation test is appropriate, can it continue? Maintenance costs? 5. Can the reform of this test method really improve efficiency? Or only in Google's corporate background and corporate culture can be feasible. 6, testing is not equal to quality. 7. In addition, this book has been mentioning the first Class citizen, reminds me of James in his speech asked a question: "There are people here, the salary is higher than the development of it?" The same? 30% Lower? "Only a few people said it was the same, and most of them were 30% lower.
A job is not a first Class citizen in addition to the salary can be seen, in peacetime discussion can also be seen. In my industry, the discussion of technical details and how to implement it must be irrelevant to the test, and many people are not bothered to discuss it with the test. Why, ask code do not understand code, ask the demand is not as good as the demand personnel.
In order for the test person to be able to criticize only the development of the Code and the requirements of the problem, Patrick in the recruitment of people, the requirements must understand the code, understand the needs of the computer is not casually will be tested. WTF, the world estimates that Google can do this kind of thing.
Look at the status of the test, how many companies are not because of the development of higher wages, afraid they waste time on the test and ask the test engineer? Even Joel on software's author in N-year-old articles (http://www.joelonsoftware.com/articles/fog0000000067.html, see the last article.) Although the article was written more than 10 years ago, but the current situation is not very different, the test salary is high point, but still less than the development of a lot. Said, this is a cheap pile of money choice Ah! It is no wonder now that more and more tests are being outsourced to Indians. Alas. Also, in the domestic situation, the development of their own development work has been pushed to the limit, their own development tasks are forced by the boss to hang, there is time for you to do unit testing? Not to mention other integrations, system tests. He was extremely repulsive to the work himself. 8, who knows the importance of doing unit testing in the life cycle of a software, but why do most companies choose not to do it? The core is the cost of the problem: 1 left to the developer's time is not much, overtime work is not finished, how can have time to write unit test, such as the company's mandatory requirements must be written, that is also fooled. 2) Even when development time permits, writing unit tests will certainly prolong the development cycle, at least as the company's bosses think. Such a cost boss can not consider saving it? 3) Set with TE these two types of job requirements are too high, generally no good company treatment and corporate culture, work atmosphere, such people will choose to leave after the search, because such people do not have to worry about finding a job. 9, EP is the abbreviation of Engineering Productivity, the meaning of engineering productivity, this team is to the entire technical team, and even the whole company to improve efficiency. In layman's words, it's a tool team. Because 工欲善其事, its prerequisite, do not underestimate the tool team, to some extent, a product with the market changes may soon wither, and a good engineering tools, vitality is much stronger, for example, the development of language is actually the most basic engineering tools. So how can a company, or delivery team, measure the productivity of a project? This measure actually determines the direction of the "EP team's work. Our own definition of engineering productivity from low to high definition is this: 1) quality, this is the most basic indicators, nothing, but also to ensure quality clearance, or a product even survival may not have. 2) at the same level of quality, the pursuit of speed. Quality clearance, it is necessary to see the speed of the iteration, you faster than the competition, you can survive. 3) The same quality and speed, the engineer's sense of well-being. If the quality also pass, the speed is also fast, but everyone is very bitter, every day overtime, repetitive work, see the future, this also does not. What is happiness? For us, it is the simple question that is not repeated.Troubled, the automatic is automatic, is not said to be fast, but certainly worry, the happiness here is worry, have the energy to pay attention to more meaningful things, rather than dealing with simple repetition of the problem every day. 4) The same quality and speed, but also a sense of happiness, and then look at growth. Did the engineers feel that they were growing up? Constantly solve problems or develop products, feel the repetition of labor or growth? In fact, the first three points have been done, the 4th must be some.  10, automated testing is how to match the current software rapid iterative agile development? What is the content of automation?  11, Google transfer mechanism is good, can learn from. google Product Quality Management has its forward-looking, the domestic already know as if the model of the PEA laboratory is to apply the model of Google. However, to achieve the effect of Google is still difficult, not even realistic. But we can partially absorb it. Summed up some reading notes: 1, such a test reform must be the entire company's uniform behavior, the need for the full cooperation of various departments after a considerable period of time to complete the precipitation. To see the company's corporate culture. 2, manual testing personnel will experience testing, experience testing can only be done under the participation of people. This part of TE will be reduced, but will not disappear. 3, add set of the position is only to assist the unit Test SWE, but in accordance with the SWE conditions are not easy to find, even if found, the treatment is more than the same as SWE, testing department in a vacuum to add a high-cost position, the boss can accept? 4, the role of TE is responsible for user experience testing, automated script testing. But in an agile fast iteration, the need to improve the situation, the automation test is appropriate, can it continue? Maintenance costs? 5. Can the reform of this test method really improve efficiency? Or only in Google's corporate background and corporate culture can be feasible. 6, testing is not equal to quality. 7. Everyone knows the importance of doing unit testing in the life cycle of a software, but why do most companies choose not to do it? The core is the cost of the problem: 1 left to the developer's time is not much, overtime work is not finished, how can have time to write unit test, such as the company's mandatory requirements must be written, that is also fooled. 2) Even when development time permits, writing unit tests will certainly prolong the development cycle, at least as the company's bosses think. Such a cost boss can not consider saving it? 3) Set with TE these two types of job requirements are too high, generally no good company treatment and corporate culture, work atmosphere, such people will choose to leave after the search, because such people do not have to worry about finding a job. 8, automated testing is how to cooperate with the current software rapid iterative agile development? What is the content of automation? 9, Google transfer mechanism is good, can learn from. 10, testing is development, development is testing. 11, eat their own dog food. 12, forecast in the near future, the treatment of test groups will be greater than equal to openGroup. 13, we do not have the overall completion of Google's cottage, but we can do Google's flagship version, the domestic version, is the Lite version is also good AH. 14, but now engage in exploratory testing the heat of a large rebound, some companies have gradually taken the exploratory as the main part of the experience test, Google's investment is more than 20%.
10. How to read Google test
