Talking about software defect management

In the test work , Defect management is one of our essential work contents . Since it's management , There is no shortage of time 、 People and management content . This article will share the basic content of defect management in software projects and some thoughts on defect management .

Pictured 1-1 Shown , Defects usually contain the following eight states ： open 、 Reopen 、 Repaired 、 Not reproduced 、 The question is repeated 、 Not a problem 、 Delayed repair and close . among , R & D personnel need to pay attention to and deal with the defects in the two states of opening and reopening , Testers need to pay attention to and deal with the repaired 、 Not reproduced 、 The question is repeated 、 It is not a problem or a delay in repairing the defects in these five states . Of course , Different enterprises have different settings for defect status , For the time being, this article takes these states as examples .

chart 1-1 Software defect state diagram

When we enter a new defect , Defects are in the initial state , That is, it is open , At this time, the person in charge of the defect is transferred to the R & D Engineer . Pictured 1-1 The marked 1 State flow direction , There are different ways to deal with defects after R & D and analysis , If it is confirmed that it is Bug, After the defect is repaired, the defect status will be transferred to repaired , At this time, the person in charge of the defect is transferred to the test engineer . If the R & D personnel cannot reproduce the problem or think it is not a problem or find duplicate defect records , Then note the reason why the backflow turns to the corresponding state . If yes Bug But there is no time to fix it in the current version , After consulting with product manager and test engineer , Defects can be transferred to the deferred repair state .

Pictured 1-1 The marked 2 State flow direction , The state flow here is bidirectional , That is, defects can flow back and forth between test engineers and R & D engineers for many times , As long as the defect is not repaired or the treatment result of the defect is not agreed by all parties , Defects cannot flow to the final state .

Pictured 1-1 The marked 3 State flow direction , The next state of defect flow is closed , That is, the final state of the defect . When the defect is verified by the test engineer that it has been repaired or the treatment result of the defect has been agreed by all parties , You can close the defect .

chart 1-2 Software defect handling flow chart

Based on defect state management , Let's take a look at the defective human collaboration process , It can be simplified into three parts , Pictured 1-2 Shown , The first is to find out the problem , Then analyze and solve problems , The last is to verify the problem again . Corresponding to the defect processing process , First, the test engineer finds the defects and records the defects , Then the R & D Engineer will analyze and deal with the defects , Finally, the test engineer verifies the processing results , If the verification passes, close the defect , If the verification fails, it needs to be transferred back to the R & D personnel for re analysis and treatment .

Through the introduction above , We learned about one of the most important tasks of test engineers ： Defect management . Of course , This article is not only to share the specific content of defect management , It is also to think about how to do a good job of defect management . In short , It is to clarify the status of defects 、 Corresponding principals and collaborative processes .

chart 1-3 Software project flow chart

Pictured 1-3 Shown , From the perspective of software project , System testing is only one part of the project , And defect management is only a part of system testing , If we want to do a good job in software project management , Or we want to do a good job in quality assurance of software projects , What to do ？

“ Identify key project nodes , Establish appropriate collaboration processes , Specify when （ node ） Who should do what .” This may be an answer .

Relevant citations ：

《 Talk about software system testing —— Problem solving 》

《 Talk about project quality assurance —— Collaborative process optimization 》