Relationship between testers and developers

This article has been published by the author Xia Jun authorized Netease cloud community.

Welcome to the Netease cloud community to learn more about the operation experience of Netease technology products.

I have been engaged in software testing for many years. I have participated in many projects, developed many projects in cooperation, and talked about the relationship between testing and development. It is more subtle to say. Sometimes I can get along with each other and sometimes have many contradictions. In fact, the root cause of the conflict is nothing more than a bug, but it originated from a bug and ended with a bug.

First, let's take a look at the entire software product lifecycle. Developers and testers correspond to different stages with different responsibilities ,:

It can be seen that the scope of testing and development is different, and there is a misunderstanding of the process and business volume. Therefore, there is a conflict in cooperation. I believe that even if we develop a role, the technical bias is also different, and we have never gone into depth and do not know another depth, for example, if a person stays in a company for less than a few months, he may comment on how the company is doing. I think a company needs to wait for at least two years to understand the company's operating model, of course, most of them should be in the ordinary category.

Often, the test has the following Voices:

1. Can this bug be seen at a glance?

2. The bugs of The New iteration version have been reproduced. Are they complete?

3. How can I be so unconscious if I fail to smoke for several times?

4. Changing a bug involves a lot of things, so I cannot evaluate it?

5. I have not verified the code. How can I secretly launch it myself?

6. How slow is problem locating, which affects efficiency?

7. Do you have to reproduce it? Do you not have to operate it on your own? In particular, You have to reproduce it several times ~~

......

Correspondingly, developers may have the following voices from time to time:

1. Is this bug a defect?

2. This is clearly not the module I am in charge of. Why is the defect under my name?

3. can I ignore repeated bugs?

4. This is indeed a problem, but won't it be so serious?

5. Positioning for half a day will result in environmental problems or third-party environmental problems, in vain!

6. This problem was left by our predecessors. Can't I change it?

7. Sister/brother: I am in a hurry to release the product. This problem is ignored first.

8. I used the xxx technology here. The YYY method and the ZZZ constraint are imposed, so this bug cannot be avoided.

......

From the perspective of projects, development and testing are a collective, because there is only one common goal, that is, to deliver high-quality and zero-defect software versions, so the relationship between each other should be well handled, we need to think differently and understand each other.

Our testers also need to constantly improve their literacy so as to maintain the relationship between the team members. The following measures can be taken to improve the overall situation of rolling in previous years:

1. do not deny the ability to develop because of a bug, improve the communication skills, only the quality of the program, do not attack the development itself, everyone likes to listen to good words, everyone likes to hear praise, occasionally, you can praise the design implementation of development;

2. when the project is about to be launched, you raise an urgent bug, which is obviously undesirable. The problem is that it needs to be exposed at the very beginning. At this time, the test requires full intervention in the project to expose serious problems in advance;

3. For bugs that can be changed and cannot be changed, you can find corresponding products, project managers, and other roles to sort out and negotiate;

4. For bugs that are difficult to reproduce, You need to paste the log information, and the description should be as concise as possible;

5. A certain degree of code skills is required to identify the problem and analyze the source code independently. When we find a bug, we are not eager to find the development location, but to enable Debug on our own to directly identify which line of code has a problem, the skills have been improved, and development will be impressive. Naturally, it will be polite;

6. strengthen our own needs and business understanding throughout the entire project stage. In reality, we have enough advantages to stay in the development stage, without collusion, and the entire business line is not tested as senior personnel;

7. Improve personal skills, broaden and deepen the test breadth and depth.

Finally, in one sentence, testing and development are the most intimate comrades-in-arms! At present, our financial department projects are very tight, and the KPI target system is under great pressure. In addition to work, testing and development can also carry out some extra-curricular activities, such as playing ball games, playing cards, and gathering meals, remember works for a better life!

The Netease cloud free trial hall provides over 20 cloud products at zero cost!

For more information about Netease technologies, products, and operations, click.

Related Articles:
[Recommendation] data hijacking at the core of the Vue framework
[Recommendation] dockerized test environment-container cluster orchestration practice
[Recommendation] tidb and MongoDB sharded cluster architecture comparison

Relationship between testers and developers