2017 Importance of Bug Prevention Blog Categories:
Bug , Chinese name defect. A word that excites software testers and gives developers headaches. Source During World War II, a computer called " Mark II " crashed due to overheating and the hardware could not keep up. It was finally discovered that the moth was electrocuted by a relay, and it was marked as " the first instance of a bug found " . People jokingly call computer errors bugs , and the work of finding bugs is called debug , that is, catching bugs!
Software bugs can be divided into several categories:
The first type of bugs can be random, and they are usually caused by a momentary oversight. Although these bugs may be difficult to prevent due to their randomness, proper analysis will help avoid them . The automated testing tool TestWriter performs use-case testing to realize real-time viewing of the execution without being on duty .
Another type of bug comes from a misunderstanding of requirements , a bug in the development environment, or simply due to a lack of relevant technology to solve the problem. The common feature of these kinds of bugs is that they all come from the developers. These bugs will persist until discovered . If bugs are discovered and fixed earlier, development costs are lower, so is it less costly to avoid bugs in the first place ? If bugs could be completely prevented, there would be no duplication of effort during development.
So what are the levels of bugs ? Here is a popular science with you , five levels :
Urgent ---- critical errors , including the following errors:
1. The crash caused by the program and the illegal exit ; 2. The infinite loop ; 3. The database is deadlocked ; 4. The program is interrupted due to wrong operation ; 5. The function is wrong and the requirement is not realized ; 7. Data communication error
Very high (very high) ---- more serious errors, including the following errors:
1. Program error ; 2. Program interface error ; 3. Constraints such as database tables, business rules, and default values without integrity ;
High (high) ---- general errors, including the following errors:
1. The operation interface is wrong, including the definition and meaning of the column names in the data window; 2. The printing content and format are wrong; 3. The simple input limit is not placed in the foreground for control; 4. The deletion operation does not give a prompt; 5 . Too many empty fields in database table
Medium - Minor errors, including the following errors:
1. The interface is not standardized; 2. The description of the auxiliary instructions is not clear; 3. The input and output are not standardized; 4. The user is not prompted for long operations. 5. The text of the prompt window does not use industry terms ; distinguishing mark
Low ( low ) ---- test suggestive questions , as follows:
1. New discovery New refers to the state when a new problem is discovered during the execution of the test.
2. Open Open refers to the state after the project leader assigns the newly discovered problems to the developers.
3. Modified Fixed refers to the state after the developer has completed the modification of the assigned problem.
4. Rejected means that when the person in charge of the project reviews the newly discovered problem, it can only be marked as this state when it is considered that the problem is duplicated with other problems or not a defect , and the reason needs to be explained. Defects should not be flagged as rejections.
5. Reopening Reopen means that the problem still exists when the modified problem is tested, and the problem is marked as this state.
6. Closed means that after verifying the modified problem, it is considered that the problem has been corrected.
Bug , Chinese name defect. A word that excites software testers and gives developers headaches. Source During World War II, a computer called " Mark II " crashed due to overheating and the hardware could not keep up. It was finally discovered that the moth was electrocuted by a relay, and it was marked as " the first instance of a bug found " . People jokingly call computer errors bugs , and the work of finding bugs is called debug , that is, catching bugs!
Software bugs can be divided into several categories:
第一类bug可能是随机的，它们通常是因为一时的疏忽造成的。尽管这些bug可能由于其随机性很难预防，但是，适当的分析将有助于避免这些bug。自动化测试工具TestWriter进行用例测试，实现无需值守，实时查看执行情况。
另一类的bug来自于需求的误解、开发环境的错误或者纯粹由于缺乏解决问题的相关技术。这类bug共同的特点是都来自于开发人员。除非被发现，否则这些bug将一直存在。如果bug发现和修正越早，开发成本越少，那么在第一时间就避免bug引入是不是成本消耗得更少？如果bug可以被完全预防，那么在开发过程中就不会出现重复工作的情况。
那么bug又分为几个级别呢？这里和大家科普一下,五个等级：
Urgent（紧急）----严重错误，包括以下各种错误：
1、由于程序所引起的死机非法退出;2、死循环;3、数据库发生死锁;4、因错误操作导致的程序中断 ;5、功能错误需求未实现;6、与数据库连接错误; 7、数据通讯错误
Very high（非常高）----较严重错误，包括以下各种错误：
1、 程序错误 ;2、程序接口错误 ;3、数据库的表、业务规则、缺省值未加完整性等约束条件 ;
High（高）----一般性错误，包括以下各种错误：
1、操作界面错误包括数据窗口内列名定义、含义是否一致；2、打印内容、格式错误；3、 简单的输入限制未放在前台进行控制 ；4、删除操作未给出提示；5、数据库表中有过多的空字段
Medium（中）----较小错误，包括以下各种错误：
1、 界面不规范；2、辅助说明描述不清楚；3、输入输出不规范；4、长操作未给用户提示5、提示窗口文字未采用行业术语；6、可输入区域和只读区域没有明显的区分标志
Low(低)----测试建议性问题,如下所示：
1、新发现New，是指在执行测试时新发现一个问题的时候的状态。
2、打开Open，是指项目负责人把新发现的问题分配给开发人员以后的状态。
3、已修改Fixed，是指开发人员完成被分配问题的修改后的状态 。
4、被拒绝 Rejecte，是指项目负责人在评审新发现的问题时，认为该问题与其他问题重复或者不是一个缺陷的时候，才可以标识为该状态,并需要说明理由。只要是缺陷都不应被标识为拒绝。
5、重新打开 Reopen，是指对已修改的问题进行测时发现该问题仍然存在则将此问题标识为该状态。
6、已关闭Closed ，是指对已修改的问题进行验证以后认为该问题已经修正。