Shulou(Shulou.com)06/02 Report--

The first realm of testing: revolving around Bug

"consciousness determines action, action determines result" is a well-known saying in management. In the first few years of testing, the author did not have this awareness, nor did he take the initiative to think about this issue, but with the experience of one project task after another, I gradually realized that this sentence was also suitable for the understanding of the realm of testing work. " Attitude determines fate "and" attitude determines everything. "many famous scholars have written books on this subject, which has basically become an undeniable truth for us, but if we really apply it to our own work and life, I am afraid it is not so simple. Admittedly, testing work, in addition to having excellent testing skills, must also have a correct testing mentality, and it is these mindsets that influence your daily work. Different mentality reflects the height of different test realm, and finally reflects different results.

Revolving around the Bug is the first of the triple realm of testing. To sum up, it can be divided into three stages: first, find the second Bug;, locate the third Bug;, and turn off Bug. The requirements for testers in these three stages are not only technically progressive, but also put forward higher requirements in terms of comprehensive quality. The three stages are intertwined. Until the end of Bug's life cycle. The requirements for the testers in the three stages around the Bug and the diagram of the life cycle from the Bug to the shutdown. This is shown in figure 2-5.

Figure 2-5 three advanced diagrams revolving around Bug

When talking about the three stages around Bug, I can't help but think of the triple realm of life mentioned by Wang Guowei, a famous Chinese scholar in Modern China: "Last night the west wind withered the trees, went up the tall building alone, and looked at Tianya Road". "when you get wider and wider, you won't regret it, and you'll be haggard for Iraq."

Looking for him thousands of degrees in the crowd, he suddenly looked back, but the man was in the dim light.

After careful consideration, I feel that there are similarities and differences between them.

The first important thing: "the west wind withered the trees last night, went up tall buildings alone, and looked at Tianya Road alone" means that "those who have achieved great achievements and great learning in ancient and modern times must first set clear goals and make up their minds to go on this long road, even if they have a long way to go." this is a painful moment for a person to find an ideal and a foothold in life in solitude. The first stage of "discovering Bug" around Bug must also have a clear and clear goal. The process of finding Bug is long, and repetition and boredom are the characteristics of work, but in order to achieve the goal, "no matter how long it is, you have to keep going" until you find piles of Bug. Especially for some occasional serious Bug, the process of reproducing Bug is like looking for a needle in a haystack, but persistence is victory. The author once spent nearly a month in a project to reproduce and solve a serious problem, and finally found the root cause of the problem in close cooperation with developers.

The second is "getting wider and never regretting, making people pined away for Iraq" means that "persistent pursuit, selfless struggle, until haggard and emaciated, even clothes become spacious, all these efforts are for the dream in my heart." Corresponding to the second-order "positioning Bug" revolving around the Bug in the soft test. At this stage, not only higher technical requirements have been put forward, but also the persistent spirit of studying assiduously, pursuing to the end, not hitting the south wall and not turning back will not stop until the cause of the problem is clearly understood. In the current domestic testing field, most companies do not require testers to do this step, but in foreign countries, especially in some well-known companies, such as Microsoft, almost all testers have in-depth debugging skills. In addition to reproducing the problem in the shortest path, it also analyzes the possible results of the problem (such as analyzing which modules will be affected by Bug), and even proposes solutions to developers. Obviously, this step requires testers to have higher design analysis ability, code debugging ability and problem-solving ability than developers. Readers, when you see this, you are relieved of the question of "whether testers should know how to program" that is often seen on the Internet.

The third is "looking for him thousands of degrees in the crowd, suddenly looking back, the man is in the dim light." This stage refers to after continuous training, many failures, a moment suddenly a little bit of empathy, understand the true meaning, found that what they want originally in their own side or after the understanding of the heart. In the eyes of others, his "suddenly looking back" is how accidental and lucky, but behind it is the diligence of hard work and the depth of ordinary accumulation, how can ordinary people persist and imagine? At this time, whether the secular goal has been achieved is no longer important, what is important is the liberation of the soul and the ownership of the soul. Corresponding to the third-order "turn off Bug" around Bug, if you only take it literally, it is very simple: the developer solved the Bug, returned to Bug, and then turned off Bug. If so, the author thinks that this concept still belongs to the first stage. The third step of shutting down Bug means that testers should actively promote developers to solve problems and assist them to solve problems after submitting a Bug. Only when problems are solved can the quality of software be improved and the ultimate goal of testers be achieved. Some of the questions submitted are strictly speaking not Bug, but a design flaw, so what should the tester do? It is necessary to take the initiative to summon relevant experts to conduct risk analysis on its impact side, and to follow up the entire resolution process of this problem. If the risk point involves changes in other professions (such as embedded software involving hardware, mechanical knowledge, etc.), it may be necessary to set up a special problem solving team to comprehensively solve the problem, until the problem of each professional direction is solved and regression verification is completed before the Bug can be closed. From the perspective of the life cycle of Bug, it is a reasonable and complete process for a Bug to go from the starting point of being discovered to the end of being closed, as shown in figure 2-6. However, in order to reach this level, it is likely that a large part of the work has been completely separated from the work of pure software testing, but the ultimate goal of testing is to give users a high-quality and reliable product. We need to have such a broad mind in order to do the product testing work more far-reaching and wider.

Then, combined with the case, the three stages around Bug are introduced respectively.

This article is excerpted from the book "Soul of Software testing: core Test Design (2nd Edition)"

By Xiao Liqiong

Published by Electronic Industry Press

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.