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

Testing and development can be said to be a pair of sins in previous lives and enemies in this life. The job of development is to build the product according to the design of PM, while testing is to find errors in the work that has been done by development. Obviously, testing this kind of work will make developers very uncomfortable, in fact, not only developers, everyone does not like the results of their own work, do not find fault with others. If testing does not pay attention to ways and methods at work, it will make the already tense relationship between test and development even worse. So testing is always easy to quarrel with developers, quarrelling with chickens and dogs, but it is not easy to get started. This scene is repeated in different companies every day.

Even though the current tests are mostly post-90s girls, they are white and beautiful, upright and responsible for their work. The developers are also big boys with great skills and good temperament. Once the two sides are at odds with each other when they work, they will eventually need the mediation of boss to make a truce.

The content of their quarrel is often the same:

Test: why hasn't the bug I mentioned been fixed?

Developer: Oh, when did you mention bug? What bug is mentioned?

Test: you didn't read the email?!

Developer: Oh, but there are so many emails, how can I see it?

Test: I have said about this bug 800 times, even pigs understand what's going on, why don't you understand?!

Developer: Oh, I don't understand. Say it again.

Test: the bug just mentioned has been repaired quickly!

Developer: Oh, but you only give me a few names, environment, steps without anything, how can I reproduce, how can I fix it?

Test: why hasn't the bug I told you been fixed for three days?

Developer: Oh, but you didn't say who was going to fix it.

To sum up, there are only a few reasons for their quarrel: either the test mentioned bug email developer did not see it, which led to the dispute that the bug was not fixed; or the test mentioned bug development could not be reproduced, or the dispute was caused by the disagreement between the two sides on the priority of bug.

In fact, these quarrels are totally unnecessary. Let me talk to you about how to do a good job of testing and get along well with developers based on my work experience.

As far as testing is concerned, bug management is a very important part of daily work, which directly determines whether testing and development can get along harmoniously.

In the past, the test added the newly discovered bug to the development task, and then the dog drove the rabbit as if to urge the developer to modify the bug submitted by himself. Developers have their own daily development tasks, especially at the beginning of the project, the work pressure is very great, if you add bug to the daily tasks of development, it will increase the pressure of development, and it is easy to confuse the work of development. The idea that you finally remember is also interrupted by the sudden bug.

In order to solve this problem, bug must be managed separately, which is not only conducive to the smooth progress of the development work, but also more convenient for testing to manage and track bug.

Achieve reasonable distribution and clear priorities when recording bug. Bug is graded according to its severity. Generally speaking, bug is divided into three levels: ordinary, important and urgent, and the specific classification can be determined according to the actual situation. Include urgent bug in the current goal and designate specific developers to fix it; important bug can be reconsidered according to product planning and current progress; ordinary bug can be left out for the time being.

This not only does not affect the progress of the main line of development, but also can better complete the bug repair work, ensure a good experience of existing products, but also reduce the friction and quarrel between testing and development. It also ensures that the test has a good management of the bug. In the later stage, you only need to track the status of the bug and file the repaired bug in time.

If all this is done, how can testing and development be the same?

Most of the time, not only do you finish the work at hand, you are working on the same team for the same goal. If you delay the work of other partners just to finish your work faster, the loss will outweigh the gain in the end.

Therefore, in daily work, we should think about problems from each other's point of view, be more considerate of each other, do a good job within the scope of our ability, solve problems, and create a comfortable problem-solving environment for each other. The other party will naturally look good in your eyes and keep in mind. Even if it is the old iniquity of the past life, the enemy of this life can still have lovers to get married.

All right, after you have finished reading the article, I will share some information with you.

Information related to interface testing

Link: https://pan.baidu.com/s/1ojpoWnpxxReR1sO2Gxy_YQ password: dgfa

Data related to performance testing

Link: https://pan.baidu.com/s/1_oZhvOIRvcz0JGcCWUGT-g password: d82b

Introduction to software testing to improve e-books

Link: https://pan.baidu.com/s/1Fp8CFE0D2p0uAZk6xcexhQ password: exna

Data related to automated testing

Link: https://pan.baidu.com/s/1yeD1EMg-HalNuRBDODGx7g password: ofdg

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.