Definition of software defect
Definition of the standard: From the inside of the product, a defect is a variety of problems such as errors and defects in the development or maintenance of the software product; from the outside of the product, a defect is the failure or violation of a certain function that the system needs to achieve
Software defect life cycle
Severity & priority
Is BUG severity and priority necessarily proportional?
Defect status
Common indicators of software defects
| Some commonly used indicators |
description |
| Defect rate (number of defects/scale) |
On the one hand, as an assessment of developers, on the other hand, it is used to analyze and prevent bugs in the development process. |
| Defect density (number of posted defects/total number of defects) |
It is mainly used to analyze the process improvement of product release. If this data is too large, it means that our release standard is too low. If this number is very low, it means that our release standard is too high. After the fact is released, bugs are allowed, so how to improve Release and release, you must use this data to measure |
| Defect repair time limit |
The timeliness requirements for repairing defects that cannot be graded are different, and they are generally used to investigate whether the development feedback problems in time |
| Defect verification time limit |
Check whether the tester verifies the resolution of the defect in a timely manner |
| Rejection rate |
Check the quality of BUG submitted by testers |
| Repeat opening rate (number of bugs opened repeatedly/number of bugs) |
Assess the developer's self-test for BUG |
| Defect Type Distribution Report |
The defect type distribution report mainly describes the distribution of defect types and sees which types of errors the defect belongs to. This information helps to attract the attention of developers and analyze why defects are concentrated in this type |
| Defect area distribution report |
The defect area distribution report mainly describes the occurrence of defects in different functional modules. This information helps developers analyze why defects are concentrated in a certain functional module. For example, if the defects are mainly concentrated in the document approval process, then it is necessary to analyze whether the workflow interface design called by the approval process is unreasonable |
| Defect status distribution report |
The defect status distribution report mainly describes the proportion of various statuses of defects, such as the percentage of Open, Fixed, Closed, Reopen, Rejected, and Delay bugs. This information helps to assess the current status of tests and products |
| Defect Trend Report |
The defect trend report mainly describes the defect situation over a period of time. If the project management is more standardized and the defect management and testing process is normal, the defect trend report can also be used to estimate the release date of the software |
Written at the end,
if you are interested in python automated testing, web automation, interface automation, mobile terminal automation, interview experience exchange, etc., you can follow the WeChat official account: [Programmer Erhei] to get an interview with a software test engineer data! My learning exchange group: 785128166 There are technical experts in the group to exchange and share~
If the article is of interest to you, please reach out to make a fortune and give me a like. Thank you for your support. Your likes are my motivation for continuous updates.