[Software testing] developers with high emotional intelligence

Testing and development can be said to be a cool of past lives. The development work is to create the product according to the PM Design, while the test is to find errors in the work completed by the development. Obviously, testing such a job will make development uncomfortable. In fact, it is not only development, but everyone does not like their own labor achievements. If you do not pay attention to the methods and methods in your work, the tight relationship between testing and development will become worse. Therefore, testing is always very easy to argue with developers, so it is difficult to get started when it is so noisy. Such scenarios are repeated in different companies every day.

Even if the current tests are mostly post-90 girls, the skin is white and beautiful, the personality is straight, and the work is serious and responsible. Developers are also big boys with high technical skills and good temperament. Once the two sides are busy, the boss's mediation is needed.

What they quarrel with is often the same:

Test: Why haven't I fixed the bug ?!

Development: Oh, when did you mention the bug? Which bugs have been raised?

Test: you have not read the email ?!

Development: Oh, but there are so many emails. How can I see them.

Test: I have told you about this bug eight hundred times. Even a pig understands what it is, why can't you understand it ?!

Development: Oh, I don't understand it. You can try again.

Test: fix the bug you just mentioned !!!

Development: Oh, but you only give me a few names, environment, and steps. How can I reproduce them? How can I fix them?

Test: the bug I told you last time has passed three days. Why haven't it been fixed ?!

Development: Oh, but you didn't tell anyone to fix it.

To sum up the reasons for their quarrel, either the bug was not found during the development of the test, resulting in a dispute arising from the failure to fix the bug, or the dispute caused by the failure to reproduce the bug development; either the two sides disagree on the priority of the bug.

In fact, these quarrels are completely unnecessary. Next I will share with you my work experience how to do a good job of testing and get along with development.

As a test, Bug management is a very important task in daily work. The quality of this work directly determines whether the test can be harmonious with development.

In the past, we used to test and add the newly discovered bugs to the development task. Then, we were eager to develop and modify the bugs we submitted. Development has its own daily development tasks, especially in the early stage of the project, which puts a lot of work pressure. If you add bugs to the daily tasks of development, it will increase the development pressure, it is also easy to confuse the development work, and the idea of hard to remember is also interrupted by sudden bugs.

To solve this problem, you must manage bugs separately. This not only helps the development work smoothly, but also facilitates the management and tracking of bugs for testing.

Make proper allocation and clear priorities when recording bugs. Classify bugs by severity. Generally, bugs are divided into three levels: Common, important, and urgent. The specific classification can be determined based on the actual situation. Add urgent bugs to the current goal and specify specific developers for fixing. Important bugs are discussed based on product planning and current progress. Common Bugs can be ignored for the moment.

In this way, the progress of the main development line is not affected, and the bug fixing work can be well completed to ensure the good experience of existing products, but also reduce the friction and quarrel between testing and development. It also ensures the good management of bugs in testing. In the future, you only need to track the status of bugs and archive fixed bugs in time.

If the above is done, how can testing and development be in the same fire?

Most of the time, you don't just finish your work. You are working on the same team for the same purpose. If you delay the work of other friends just to complete your work more quickly, the final goal will also be worth the candle.

Therefore, in daily work, I think about the problem from the perspective of the other party, understand the other party more, do a good job within the scope of my ability, and solve the problem well, create a comfortable environment for the other party to solve the problem. The other party naturally looks at you and remembers it. Even in the past, the strangers of this world can become the same.

Now, after reading the article, I will share some information with you.

Interface Test Materials

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

Performance Testing Materials

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

Getting started with software testing to improve e-books

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

Automated Testing Materials

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

[Software testing] developers with high emotional intelligence