Development and testing in software development-next

This article introduces the necessity of testing and goes back to the "Conflict" between development and testing. In fact, this conflict is essentially because performance management emphasizes bugs caused by developers too much, this "excessive emphasis" must be emphasized by testers. So, the conflict began to emerge. Developers said that this is not a bug, or I cannot reproduce it. They also said, why are you always raising bugs? Are you not satisfied with me. Over time, "contradictions" have emerged, intensified, and the product quality has declined ......

 

From the perspective of the leadership, of course they want to develop products without any bugs. In this way, I don't even need to configure testers, and the cost is much lower. Of course, most leaders also know that this is impossible. Instead of selling products badly due to reduced product quality, it is better to have several testers. With the support of testers, there is a "Conflict". I think many leaders of the company have handled the problem well. However, I still want to briefly introduce the solution of our company:

1. bind the product sales performance with the development and testing, that is to say, the sales are good, there are more bonuses, of course, the sales are good, the product quality is also good, then we have to cooperate with each other in development and testing. Currently, many companies have fixed development and testing salaries and bonuses, so they will not increase their bonuses due to good performance. Our company has clearly stipulated that a few percent of the profit of this product is development and a few percent of the profit is testing, which gives development and testing a reassurance from the system, improve product quality.

2. in the performance appraisal of each sales staff, add other appraisal items to reduce the generate weight of each thousand lines of bugs, and increase the bug fixing success rate, such as the percentage of bugs that appear again in similar functions, cooperation with testers and other assessment items. In this way, developers will begin to attach great importance to communication with testers, because they began to know that the cooperation with testers determined the money they could get. (Someone just asked how to get these values similar to the bug fixing success rate, which can be obtained by a better bug management tool. We automatically generate the values in the devsuite system.)

3. Of course, testers also need to add some new assessment items, such as whether the bug description can be clearly viewed by developers.

 

Through these measures, the efficiency of development and testing has been greatly improved, thus improving the product quality. In philosophy, contradictions are the driving force for the development of things. Learning to use these contradictions to make the company develop healthily and steadily is what every successful company needs to learn. Our company cannot be very successful now, but we are moving forward in this direction.

Preface: A friend commented: (The following is the original story)

The software testing department is the assistance Software Development Department to make the product ready!

They are not opposite, but mutual help.

In reality, it is often seen that the R & D department looks down on the Testing Department, while the testing department calls the R & D department, saying how many problems exist in the product...

Remember that the product is made, not tested!

The test team must correct their positions to help the R & D team do a good job of the product and improve the product quality! Locate the problem and follow up to solve the problem! Do not break down the relationship with R & D personnel!

Always remember: everyone is a team! Everyone has a common goal: to make the product ready! Development and testing should recognize that everyone is a team and a whole. Only by close cooperation can we make the product ready.

In fact, I still agree with the general direction. Indeed, development and testing must work closely together to make full use of the team spirit in order to make the product ready, so that the product can be sold well and the company can develop, so I think this comments can be considered as an ideal relationship between development and testing. However, to realize this ideal relationship, the two departments alone cannot achieve it completely. We need to formulate a reasonable system at the company level to fundamentally solve the problem. Assume that the quality of the Code (that is, the number of bugs per thousand lines) is very high in the assessment I have given for development, and the tester finds that the number of Bugs has a high weight each day, there will inevitably be some conflict between development and testing. In fact, they also know that cooperation is required and there is no conflict between them, but they are working on their own. You give me so many bugs, I will get less money, and I will get less money if I don't give you so many bugs.
Therefore, the purpose of writing this article is to make the development and testing reach an ideal relationship, rather than the relationship between development and testing.