Http://bbs.pfan.cn/post-305427.html
1. Suggestions on bug classification:
Currently, the severity of a bug in a project is divided into five levels. According to the specifications defined in cmmi5, the severity of a bug can be divided into three to five levels. We recommend that you divide the severity of a bug into four levels, they are serious, primary, secondary, and mild.
● Level 1, critical, severe (can correspond to "very serious" in the current bug system "):
Major problems: the system cannot be executed, crashed, or has insufficient resources, the application module cannot be started or exited abnormally, and cannot be tested, resulting in system instability.
The details can be basically divided:
○ Severe screen capture
○ Memory leakage
○ User data loss or destruction
○ System crash/freeze
○ The module cannot be started or exited unexpectedly
○ Serious numeric calculation error
○ Seriously inconsistent functional design and requirements
○ Errors that may result in failure to test other functions
● Level 2, Major, main (corresponding to the "Main" in the current bug System ")
The main problems are: affecting system functions or operations. The main functions have defects, but do not affect system stability.
The details can be basically divided:
○ Function not implemented
○ Function Error
○ System refresh Error
○ Incorrect voice or Data Communication
○ Slight numeric calculation error
○ The functions or services provided by the system are obviously affected.
● Level 3, minor, secondary (can correspond to "secondary" in the current bug System ")
General problems: interface and performance Defects
The details can be basically divided:
○ Incorrect operation interface (including whether the column name definitions and meanings in the data window are consistent)
○ Incorrect display of Boundary Conditions
○ Information error (including information not provided or information error)
○ No progress prompt for long operation
○ System not optimized (performance problems)
○ Incorrect cursor jump settings and incorrect mouse (cursor) Positioning
● Level 4, trivial, minor (can correspond to "minor and suggestion" in the current bug System ")
TIPS: Usability and recommendations
The details can be basically divided:
○ Interface format and other non-standard
○ The auxiliary description is unclear.
○ User not prompted During Operation
○ The input and read-only areas do not clearly differentiate
○ Incorrect product understanding
○ Small issues such as unordered text
○ Suggestions
Note: For structure and hardware problems, because the product testing department only performs secondary testing, when such problems are encountered, they are all located in the "severe" level ", the details should be confirmed by relevant personnel of the structure and hardware departments.
Http://blog.cnw.com.cn/index.php/20937/viewspace-1802
Severity Level:
- Level 1 (blocker): causes an error that prefers to "Suspend" or "crash" the system;
- Level 2 (critical): errors that cause the software to "Suspend" or "crash;
- Level 3 (Major): errors that fail to complete the features defined in the software specification;
- Level 4 (normal): errors that do not conform to the definition of the Software specification;
- Level 5 (minor): displays errors;
- Level 6 (trivial): Other "minor" errors (such as text errors );
- Level 7 (enhancement): enhancement or improvement.
Priority:
- 1. The resolve immediately defect must be resolved immediately.
- 2. Normal queuing (normal Queue) Defects need to be properly queued for repair or included in the software release list.
- 3. Not urgent defects can be corrected at convenience.
Bugfree2.x version, bug severity level default is 4 level, priority is also 4 level, but are displayed as numbers, if you want to modify to Chinese, need to modify lang/ZH_CN_UTF-8/_ Common. php file:
/* Bug severity. */<br/> $ _ Lang ['buckets'] = array <br/> (<br/> ''=> '', <br/> 1 => '1. severe ', <br/> 2 =>' 2. main ', <br/> 3 =>' 3. secondary ', <br/> 4 =>' 4. minor ', <br/>); </P> <p>/* bug priority. */<br/> $ _ Lang ['bugpriorities '] = array <br/> (<br/> ''=> '', <br/> 1 => '1. urgency ', <br/> 2 =>' 2. as soon as possible ', <br/> 3 =>' 3. on time ', <br/> 4 =>' 4. on Demand ', <br/> );
If notbook.exeor ultraedit.exe is modified and saved, this error may occur during running:
Cannot modify header information-headers already sent ....
Because of the file format problem, a nasty utf8 header (BOM) is automatically added and three bytes are added. A good person writes a knife program to remove it:
Http://www.shopex.cn/tools/bom_out.php