The definition of software defects
error
Still exist in the documentation representation or coding errors
defect
Tags present in the system or hardware errors
BUG
Differences in actual performance measured object and user needs explicit or implicit demand of
-
-
- Function to achieve error
- Function realization missing
- Superfluous functions to achieve
- Functions to achieve good
-
Fail
Due to the defect leads to abnormal function of the excitation, the phenomenon can not be used (dynamic, not necessarily occur)
Cause of the defects
- Demand expressed understanding, decoding process with errors
- System architecture design error caused
- Development process, lack of effective communication and supervision
- Programmers coding errors generated during
- Software development tools, the problem itself
- Software requirements, increasing complexity
- Does not meet the needs of the user, even if there is no sense in itself an error
Defects in written format
- Defects ID: field uniquely represent defects, typically use Arabic numerals, unrepeatable ID defect, and not take
- Summary Description: general description or the appearance of defects present in the form, to facilitate the rapid estimation cause defects Developer
- Find: defects found staff generally test engineer, is also possible that the developer of the project, such as developers, project managers, maintenance personnel, and even customers
- Find Time: Time defects found
- Repair time: bug fixes time
- Belongs version: found version of defects, easy to post count the number of defects found between different versions, as well as to determine the risk of release of a test version
- Belongs modules: Defect or business where the function module, to facilitate post-statistics for each feature or defect distribution service module, thereby facilitating investment in regression testing to determine the allocation of resources or research and development
- Defect state
The present state of defects, generally classified into 6
new: When the defect has not yet entered defect management process, defined as new, such as the newly discovered or newly submitted bug
open: After confirmation confirmation is BUG, officially entered the defect management process,
fix: developers thought that BUG, and do a repair activities,
ciose: defect after checking to confirm that has been repaired or without treatment
reject: Developers need to BUG open state judge, if the defect is confirmed, you will need to repair activities, if changes in demand due to the reason, design changes as a result of a defect does not exist, you can reject a secondary defect
reopen: when to close a defect fix or repair of failed or recurrence open again
- Defect severity
Defects caused by the severity of the consequences
low: the consequences of defects result is not very serious, in general, just make the user feel inconvenient, unsightly and other feelings interface
medium: general typos, incorrect fonts, error, mistake or sub-functions to achieve redundancy
high: a specific function is not working, such as query function error, sorting errors
very high: lead to large-scale features are not available
urgent: a large area of function can not be used to terminate the error, initialization error
- Priority defects: developers have confirmed that the decision to repair the defect has time
- Description: summary description of the supplement, a procedure defects generated test data, etc. System screenshot
- Further processing by: Next defects by whom