Software defect management - a must for testers

Software defect definition

Software defect （Defect）, Often called Bug. So called software defects , That is, there is a problem in the computer software or program that destroys the normal operation ability 、 error , Or hidden functional defects . The existence of defects will lead to software products can not meet the needs of users to some extent .IEEE729-1983 There is a standard definition of defects ： From the inside of the product , Defects are errors in the development or maintenance of software products 、 Problems and so on ; From the outside of the product , A defect is the failure or violation of a function that the system needs to achieve .

Cause and root

In the process of software development , Software defects are inevitable . So what are the main reasons for software defects ？ From the software itself 、 Team work and technical problems , We can understand the main factors that cause software defects .

The generation of software defects is mainly determined by the characteristics of software products and the development process .

Software itself

1. The demand is not clear , Cause the design objective to deviate from the customer's requirements , Thus causing defects in function or product characteristics .

2. The system structure is very complex , And can not be designed into a good hierarchy or component structure , The result is unexpected problems or system maintenance 、 Difficulties in expansion ; Even if it is designed as a good object-oriented system , Because of the object 、 Too many classes , It's hard to complete a variety of objects 、 Combinatorial testing of class interactions , And some parameter passing is hidden 、 Method call 、 Object state change, etc .

3. The boundary of program logical path or data range is not considered fully , Some boundary conditions are omitted , Causing capacity or boundary errors .

4. For some real-time applications , It needs careful design and technical treatment , Ensure accurate time synchronization , Otherwise, it is easy to cause incongruity in time , Problems caused by inconsistency .

5. Self recovery after system crash or remote backup of data are not considered 、 Disaster recovery and so on , Thus, system security exists 、 Hidden dangers of reliability .

6. The complexity of the system operating environment , Not only are the computer environments that users use ever-changing , Including various operation modes of users or various input data , It is easy to cause some problems in a specific user environment ; In the practical application of the system , Large amount of data . This may cause strength or load problems .

7. Because there are many communication ports 、 The contradiction between access and encryption , It will cause problems such as system security or applicability .

8. The adoption of new technologies , May involve technical or system compatibility issues , Without considering .

Team work

1. During the system requirements analysis, the customer's requirements are not clearly understood , Or there are some difficulties in communicating with users .

2. Developers at different stages do not understand each other consistently . for example , Software designers' understanding of requirements analysis is biased , Programmers do not pay enough attention to some contents of the system design specification , Or there are misunderstandings .

3. For design or programming assumptions or dependencies , Relevant personnel did not fully communicate .

4. The technical level of the members of the project team is uneven , More new employees , Or insufficient training and other reasons are also easy to cause problems .

Technical problems

1. Algorithm error ： Failure to give correct or accurate results under given conditions .

2. Grammar mistakes ： For compiled language programs , The compiler can find such problems ; But for interpretive language programs , Can only be found when the test runs .

3. Calculation and accuracy problems ： The result of calculation does not meet the required accuracy .

4. The system structure is unreasonable 、 Algorithm selection is unscientific , Causing poor system performance .

5. Interface parameter pass mismatch , Cause module integration problems .

The problem of project management

1. Lack of quality culture , Not paying attention to the quality plan , For quality 、 resources 、 Mission 、 The balance of cost is not well grasped , It is easy to squeeze out requirements analysis 、 review 、 test 、 Wait for the time , There will be many defects left .

2. The requirements of customers are not very clear during system analysis , Or there are some difficulties in communicating with users .

3. Short development cycle , Demand analysis 、 Design 、 Programming 、 Testing and other work cannot be carried out completely according to the defined process , Not enough work , The result is not complete 、 inaccurate , More errors ; Cycle is short , It also puts too much pressure on all kinds of developers , Cause some human error .

4. The development process is not perfect , There are too many randomness and lack of rigorous internal audit or review mechanism , It's easy to cause problems .

5. Incomplete documentation , Inadequate risk estimation, etc .

Defect status

1.Submitted: Submitted defects

2.Open : confirm “ Defects submitted ”, Waiting to be dealt with

3.Rejected: Refuse “ Defects submitted ”, No need to repair or not a defect

4.Resolved : The defect was repaired

5.Closed : Identify the defects that have been repaired , Turn it off

Severity classification of defects

1.Critical： Unable to perform normal or important functions . Or endanger personal safety .

2.Major： Seriously affect the realization of system requirements or basic functions , And there is no way to correct it .（ Reinstalling or restarting the software is not a corrective measure ）

3.Minor： Seriously affect the realization of system requirements or basic functions , But there are reasonable corrections .（ Reinstalling or restarting the software is not a corrective measure ）

4.Cosmetic： Make the operator inconvenient or trouble , But it does not affect the execution of work functions or important functions .

5.Other： Other mistakes .

Priority of defects

1.Resolve Immediately： The defect must be solved immediately .

2.Normal Queue： Waiting for software to be queued or released normally .

3.Not Urgent： Defects can be corrected at your convenience .

The house needs to be built layer by layer , Knowledge needs to be learned at one point one . We should lay a good foundation in the process of learning , More hands-on practice , Don't talk much , The last dry goods here ！ I stayed up late to sort out the stages ( function 、 Interface 、 automation 、 performance 、 Test open ) Skills learning materials + Practical explanation , Very suitable for studying in private , It's much more efficient than self-study , Share with you .

Get off w/x/g/z/h： Software testing tips dao

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .