51Testing软件测试论坛

 找回密码
 (注-册)加入51Testing

QQ登录

只需一步,快速开始

微信登录,快人一步

手机号码,快捷登录

查看: 4361|回复: 1
打印 上一主题 下一主题

[原创] 如何写缺陷报告(翻译)

[复制链接]

该用户从未签到

跳转到指定楼层
1#
发表于 2009-9-13 23:05:15 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
Bug reports should include following basic things.
缺陷报告应该包含以下基本项:


1. Bug summary
2. A little more description than the Bug summary
3. Pre-condition & Steps to re-produce
4. Actual result
5. Expected result
6. Severity & Priority
7. Any screen shots, AUT (Application under test) logs.
8. AUT Version on which this defect\issues arises.
9. Frequency of the defect. Always\Sometime

1.缺陷概要
2.简要的缺陷描述
3.产生缺陷的先决条件及重现的步骤
4.实际结果
5.预期结果
6.严重性及优先级
7.必要的屏幕截图,及AUT日志
8.应用程序测试在版本上产生的错误
9.标记该缺陷出现的频率。 经常/偶尔



Bug reports should be such that the developers get all the information they require to reproduce the defect. Here are some handy tips to do this.

缺陷报告应该使开发人员获得缺陷重现的所有信息。可以从以下有几点考虑:


1. Review each bug report yourself before filing it. Ask yourself these simple questions during this review
- Does the summary convey the gist of the defect?
- Have I put in all the information that I have collected for troubleshooting for this defect?
- Can I do anything else to help the developers?
- Is anything in the bug report creating confusion?
- Is the severity & priority justified?
- Am I putting in too many attachments? All of them are really required?

1.在整理每个缺陷文档的之前先检查一遍。问问自己以下几个问题:
- 总结是否描述清楚了缺陷的要点?
- 我是否将所有的缺陷的信息整理好了?
- 我还可以再做什么让开发人员更了解问题所在?
- 严重性和优先级是否合理?
- 我是否添加了过多附件? 所有添加的是否都是必须的?


2. You will encounter defects that are not always reproducible, or not reproducible on all environments (Operating System, Database, etc). Mention your findings clearly. These defects have the highest probability of being marked invalid. Handle such defects with extra care and make sure you put in every piece of information in there.

2.你经常会遇到一些不能重现或者在所有的环境中都不能重现的缺陷(操作系统,数据库,等等)。这样的问题你要提出。那些缺陷很可能被标记无效。要加倍消息这样的报告,确保重现的每条信息都完整。


3. Write that defect at the very next moment you find it. If you postpone it, you will forget some thing or the other, or spend more time in re-reproducing the issue.

3. 如果该缺陷第二次被发现。 如果你延迟,你很可能会忘记一些信息或者其他,那样的话你将要花更多时间去重现这个问题。


4. While you are testing integration of more than one application or End to end testing which involves more than one application, make sure you specify correct version of all the application used.

4.当你整个一个或多个应用程序时,确保你指定的版本正确。


Original Source: http://www.sqaforums.com/showflat.php?Cat=0&Number=561837&an=0&page=0#Post561837

BugReport_Template.rar(10.6 KB)
附件:
BugReport_Template.rar
[时间:2009-9-13 10:37 PM - 下载次数:0]
分享到:  QQ好友和群QQ好友和群 QQ空间QQ空间 腾讯微博腾讯微博 腾讯朋友腾讯朋友
收藏收藏
回复

使用道具 举报

该用户从未签到

2#
发表于 2009-10-2 23:56:13 | 只看该作者
dddddddddddddddddddddddddddddddd
回复 支持 反对

使用道具 举报

本版积分规则

关闭

站长推荐上一条 /1 下一条

小黑屋|手机版|Archiver|51Testing软件测试网 ( 沪ICP备05003035号 关于我们

GMT+8, 2024-11-11 15:46 , Processed in 0.069011 second(s), 28 queries .

Powered by Discuz! X3.2

© 2001-2024 Comsenz Inc.

快速回复 返回顶部 返回列表