报BUG时可以首先要确认是不是Bug,依据是Functional Specification和正确的理解;其次正确判断Bug的错误级别。一般情况下要求对Bug进行交叉验证(Verify),力求再现。对严重的Bug要考虑多种情况的交叉验证 :
测试人员交叉验证
测试的机器交叉(同一个操作系统和浏览器)验证
测试的平台交叉 ( Windows 9x, Windows NT 和 Windows 2000等) 验证
不同的浏览器 (IE , NS)验证对得到验证、确实存在的Bug及时报到QA Forum中;
标题、测试步骤、结果等应描述准确;
应附的各项信息应完整准确,即及时记录Bug发生的具体环境( 通过图片、系统信息来描述)、操作步骤
增强个人理解和创造性的测试,不断完善Case表。
尽力在报告中分析出错误产生的原因。
下面是详细描述:
1。Bug levels:
a. 10:minor --spelling ,wording,etc,errors;
b. 20:major--A bug does not affect the system usage;
c.30:critical--A feature doesn't work,bugs that make you can not continue your testing
d.40:fatal--The bug that cause system or browser or application crash,make the system do not work.
2. Bug title:The title shoule be clear and accurate to summarize the bug including all key words.
3. Test environment : Version: the version of the project
module: select a module from the list;
browser: select a browser from the list;
OS: input the os,whick the bug occured
4. description: write every step clearly and accurately and always keep a question in your mind:are there other conditions related with this bug? describe the results clear; how many times is this bug occurred?
5.change status: shoule add a comment .we can reopen it without verifying if developers write status like this "it is not bug"作者: 网络游侠 时间: 2006-1-17 19:51
现在提Bug基本上都用工具,细想下没工具支持的化,管理很麻烦的,通常分就是优先级1---2---3; 严重也是1---2---3, 呵呵!