1) Bug levels:
S1: Fatal: The bug that cause system or browser or application crash, make the system do not work
S2: Critical: A feature doesn't work, bugs that make you can not continue your testing.
S3: Major: A bug that does not affect the system usage
S4: Minor: Spelling, wording, etc. error
2) Bug title:
The title should be clear and accurate to summarize the bug including all key words.
Flag “language: ” and module name
3) Test environment:
Version: the version of the project
Module: select one module from the list
OS: input the OS, which the bug occurred
Browser: select one browser from the list
Hardware: CPU, chipest, memory
Device: Device's mode, firmware
4) Description:
- Write every step clearly and accurately and always keep a question in you mind:are there other conditions related with this bug?
- Type the expect result completely
- Describe the result clear
- How many times is this bug occurred.
The description of the bug must be detail and clear. And screenshot and other required attachments are not missed.
5) Change status:
Should add a comment. We can't reopen it without verifying if developers write comments like “It is not bug ”
source :
http://blog.csdn.net/doven/archive/2008/02/28/2126019.aspx
其他找到的定義:
http://sqa.fyicenter.com/FAQ/Why-Bugs-in-Software/Rules_for_bug_level.html
沒有留言:
張貼留言