Because it is a sudden thought to record something, so today to see what to write, hope for themselves and refueling partners a little help.
The author is still in the study stage, so these things are excerpted from other great gods or after reading their own summary, the wrong place also please forgive me.
Read a predecessor's article to define a tester as a bug master it's too reasonable and too interesting. The Manual of the Master of Insects
Common categories of bugs:
CALSS A:
Code Error
Design flaws
Interface optimization
Configuration related
Installation deployment
Performance issues
Standard specification
Class B:
Functional Class (function)
Performance class
UI (Interface)
Compatibility
Defect Level:
Fatal: Causes the system to fail to run, data security leaks
Severe: Easy to correct abnormal conditions, easy to repair faults, unacceptable appearance defects
General: does not affect the normal operation, to the appearance, the next procedure has the big influence
Slight: slight effect on the appearance of the product and the following procedure
Suggestion: Increase the user experience goodwill or other constructive comments
As more and more problems arise and more problems need to be addressed, you need to know the priority of handling the problem:
Priority division:
Low--"in--" high--"emergency
Delay processing-"normal queue-" priority treatment-"emergency treatment
High bug level is not necessarily a priority, low is not necessarily not a priority.
Processing Flow:
Submit bug--"Confirm bug--" distribution or transfer bug--"processing bug--" regression test (verification)--"Close the bug
Insect (bug) classification, handling bug process