当前位置:网站首页>[software testing] 02 -- software defect management
[software testing] 02 -- software defect management
2022-07-05 07:05:00 【Derived planet】
Software defect management
Because of its own characteristics and current development mode , The defects hidden in the software cannot be eradicated . Software testing is to find defects in software , Feedback to developers to make changes , So as to ensure the quality of the software , Therefore, software testing requires testers to have a deep understanding of software defects . This section will explain in detail the relevant knowledge of software defects .
1. The cause of software defect
Software defects are commonly referred to as Bug, It means in software ( Including programs and documents ) Problems that affect the normal operation of the software .IEEE(Institute of Electrical and Electronics Engineers, Institute of electrical and electronic engineers )729—1983 Standards have a standard definition of software defects : From the inside of the product , Defects are errors in product development or maintenance 、 Problems and so on ; From the outside of the product , A defect is a failure or violation of a function during the operation of a system . The generation of software defects is mainly determined by the characteristics of software products and the development process , For example, the demand is not clear 、 Requirements change frequently 、 The level of developers is limited . It comes down to , The main causes of software defects are as follows .
(1) Unclear needs . The software requirements are not clear or the developers do not understand the requirements clearly , It leads to the deviation of software design from the customer's requirements , Cause a defect in a software function or feature . Besides , In the development process , Frequent changes in customer requirements will also affect the final quality of the software .
(2) The software structure is complex . If the software system structure is complex , It's hard to design a framework with a good hierarchy or component structure , This leads to software development 、 expand 、 Difficulties in system maintenance . Even if you can design a good architecture , Complex systems also hide the problem of interaction when they are implemented , And lead to hidden software defects .
(3) Coding problem . In the process of software development , The level of programmers is uneven , Coupled with the lack of effective communication and supervision in the development process , The problems are accumulating , If we can't solve these problems one by one , It will lead to a lot of defects in the final software .
(4) The duration of the project is short . Now most software product development cycle is very short , The development team should complete the development of software products in a limited time , The pressure is very high , So developers are often tired 、 High pressure 、 Developing software in a disturbed state , In this state , The attitude of developers towards software problems is “ If it's not serious, it won't be solved ”.
(5) Use new technology . modern society , Every technology is changing with each passing day . When using new technology for software development , If the new technology itself is insufficient or the developers are not good at mastering the new technology , It also affects the development process of software products , Cause software defects .
2. Classification of software defects
There are a lot of software defects , Defects can be divided into different types from different angles .
According to the type of test, software defects can be divided into interface classes 、 Functional class 、 Performance class 、 Security class 、 Compatibility class, etc .
According to the severity of defects, defects can be divided into serious 、 commonly 、 secondary 、 Suggest .
According to the priority of defects, defects can be divided into immediate solutions 、 High priority 、 The normal line 、 Low priority .
According to the different stages of defects, defects can be divided into requirements stage defects 、 Frame stage defects 、 Design phase defects 、 Coding phase defects 、 Test phase defects .
Software defects are divided into different categories according to different standards , Concrete as table 1 Shown .
3. Software defect handling process
During software testing , Each company has developed a software defect handling process , The software defect handling process of each company is different , But they follow the same basic process , All have to be submitted 、 Distribute 、 confirm 、 Handle 、 Retest 、 Close and so on , Pictured 2 Shown .

(1) Submit : After the testers found the defect , Submit defects to test team leader .
(2) Distribute : After the test team leader receives the defect submitted by the tester , Hand it over to the developers .
(3) confirm : After the developer receives the transferred defect , We will discuss with the team and even the tester , Determine whether the defect is a defect .
(4) Refuse / delay : If after consultation , If the defect is not a real defect, it will be rejected , Close defects ; If after consultation , Make sure it's a real flaw , You can select immediate treatment or deferred treatment according to the severity or priority of defects .
(5) Handle : Developers modify defects .
(6) Retest : After the developers fix the defect , The tester retested ( Retest ), Check if the defect has actually been modified . If not properly modified , Then submit the defect again .
(7) close : After the testers retested , If the defect has been corrected correctly , Then close the defect , The whole defect treatment is completed .
4. Software defect report
In the actual software testing process , When submitting software test results, testers will follow the template specified by the company (Word、Excel、 Defect management software, etc ) Record the details of the defect and generate a defect report , Each company's defect report template is different , But it usually includes the number of defects 、 type 、 severity 、 priority 、 Test environment, etc , Sometimes there are suggestions from testers .
The following matters shall be paid attention to when preparing the defect report .
(1) Each defect has a unique number , This is the identification of the defect .
(2) Defects need to be reproduced .
(3) A defect generates a report .
(4) The defect report shall be neat 、 complete .
5. Common software defect management tools
Software defect management is a very important link in software development project , Choosing a good software defect management tool can effectively improve the progress of software projects . There are many software defect management tools , Free of charge 、 There are all kinds of charges , Here are some common software defect management tools .
1.Bugzilla
Bugzilla yes Mozilla The company provides a free software defect management tool .Bugzilla Can establish a complete defect tracking system , Including defect tracking 、 Record 、 Defect report 、 Deal with the situation, etc . Use Bugzilla When managing software defects , Testers can be in Bugzilla Submit defect report on ,Bugzilla The defect will be transferred to the corresponding Developer , Developers can use Bugzilla Make a worksheet , Indicate the priority of things to be done 、 Scheduling and tracking .
2. ZenTao
Zen is an excellent project management software made in China , It integrates product management 、 project management 、 Quality management 、 Defect management 、 Document management 、 Organization management and affairs management in one , It is a project management software with complete functions , Perfectly covering the core process of project management . Zen is divided into professional and open source versions , The professional version is a paid software , Open source is free software , For daily project management , The open source version is enough .
3.Jira
Jira yes Atlassian Project and practice tracking tools developed by the company , It is widely used in defect tracking 、 Customer practice 、 Demand collection 、 Process approval 、 Task tracking 、 Work areas such as project tracking and agile management .Jira Flexible configuration 、 Comprehensive function 、 Simple deployment 、 Expand and enrich 、 Easy to use , It is based on Java Architecture management tools .
Jira Software has two highly recognized features : The first 1 Yes Atlassian The company provides defect tracking service for the open source project free of charge ; The first 2 One is that users are buying Jira The source code will also be purchased when using software , Convenient for secondary development .
边栏推荐
- Sum of two numbers, the numbers in the array are converted to decimal, added, and output inversely
- PR automatically moves forward after deleting clips
- .net core踩坑实践
- Literacy Ethernet MII interface types Daquan MII, RMII, smii, gmii, rgmii, sgmii, XGMII, XAUI, rxaui
- 【软件测试】05 -- 软件测试的原则
- Error: "mountvolume.setup failed for volume PVC fault handling
- 小米笔试真题一
- Vscode configures the typera editor for MD
- SOC_SD_CMD_FSM
- Get class files and attributes by reflection
猜你喜欢
随机推荐
npm install -g/--save/--save-dev的区别
IPage能正常显示数据,但是total一直等于0
IPage can display data normally, but total is always equal to 0
摄像头的MIPI接口、DVP接口和CSI接口
能量守恒和打造能量缺口
Cloud native related technology learning
[MySQL 8.0 does not support capitalization of table names - corresponding scheme]
iNFTnews | 喝茶送虚拟股票?浅析奈雪的茶“发币”
PHY drive commissioning --- mdio/mdc interface Clause 22 and 45 (I)
Integer to 8-bit binary explanation (including positive and negative numbers) scope of application -127~+127
SOC_SD_CMD_FSM
An article was opened to test the real situation of outsourcing companies
[nvidia] CUDA_ VISIBLE_ DEVICES
【无标题】
namespace
Vscode configures the typera editor for MD
Use the Paping tool to detect TCP port connectivity
PHY drive commissioning - phy controller drive (II)
使用paping工具进行tcp端口连通性检测
Mid 2022 documentary -- the experience of an ordinary person


![[MySQL 8.0 does not support capitalization of table names - corresponding scheme]](/img/ea/a1e0722c43f56aff3e79f95c99ba8a.png)






