Source tracing-Do not forget the quality

Sometimes, when a few people discuss a topic, one of them suddenly thinks of another thing, or another person joins in, and the discussion is getting increasingly intense, so everyone is not interested, however, the content of the discussion is getting farther and farther away from the topic, and later I forgot what topic I was about to discuss. We may have encountered such a situation. It's okay if you are chatting. If it is to solve the problem, it will waste time and fail to achieve the goal.

In our work, this phenomenon also exists. For example, software testing is designed to discover defects, whether it is review PRD/spec, design test plan, test case design, and test automation. "Discovering defects" is the foundation of software testing. We cannot forget this foundation when doing testing. Sometimes, when testing automation, We are prone to "Forgetting" things. This situation is caused by the following reasons:

1. At the beginning, I did not know the purpose of testing automation, but automated for automation.
2. In the process of automated development, I gradually forgot my original ideas and objectives, and became more and more admired for technologies. I got into a deeper and deeper technology, and pursued frameworks and popular technologies, the problem is not solved. In other words, a simple method is used to solve the problem, but several times the effort is used to achieve it.
3. The pursuit of pure numbers, for example, has been staring at how many test cases have been automatic, but it is unclear whether the test results are reliable. Sometimes, we know that VP has risk, but we don't want to solve it. It is also a matter of self-learning.

 Therefore, remind yourself of the following points during the test:

1. Testing is to discover as many defects as possible as early as possible.
2. To do things, we do not worship technology. Instead, we must closely grasp our goals and strive to be concise, effective, and get twice the result with half the effort.
3. In the process of testing automation, the quality is still the foundation, and we must never exchange the quality for the degree of automation. The foundation of testing automation is still test cases. After all, testing tools are tools and testing tools that do not think about, and 70% defects still require human intelligence and thinking.

 Policy: Quality-oriented, supplemented by tools; tool first, after labor disconnection

1. In the face of any test task, first of all, we need to use an effective method to complete the test. That is, we can use test tools and automation to automate the test.
2. During implementation, people are the deciding factor. They always focus on the center of "quality", constantly think about it, constantly improve test strategies and methods, and continuously improve the coverage rate of test cases.

[Another example is the story of Motorola. In Motorola's strategy, the most thorough failure case is the so-called global star program, which means that technology is far beyond the market demand and can be understood as a super-technical strategy failure; now, the mobile phone business of motorcycles is another kind of failure, that is, the technology is far away from the needs of the market and can be understood as a failure to abandon the technology strategy. According to the Chinese saying "success, failure, or failure", this famous sentence of the 2000-year-old battle of China can be used to explain the success or failure cases in the world today. The reason why Motorola succeeded was that it had created the mobile age in technology. It was the evolution of human communication from the limited age to the wireless network age, which completely changed the way humans communicate, he became the leader in the wireless market and an absolute leader. It is a pity that successful people always like to play games with "Birds and birds". When the market is done, they forget their most successful strategies and core advantages. ]