How to Use a Bug Tracker
来源:互联网 发布:淘宝背景图 编辑:程序博客网 时间:2024/06/03 12:11
How to Use a Bug Tracker
Matt Doar
WHETHER YOU CALL THEM bugs, defects, or even design side effects, there is no getting away from them. Knowing how to submit a good bug report, as well as what to look for in one, are key skills for keeping a project moving along nicely.
A good bug report needs to convey three things:
• How to reproduce the bug, as precisely as possible, and how often this will make the bug appear
• What should have happened, at least in your opinion
• What actually happened, or at least as much information as you have recorded
The amount and quality of information reported in a bug says as much about the reporter as it does about the bug. Angry, terse bugs (“This function sucks!”) tell the developers that you were having a bad time, but not much else. A bug with plenty of context to make it easier to reproduce earns the respect of every- one, even if it stops a release.
Bugs are like a conversation, with all the history right there in front of every- one. Don’t blame others or deny the bug’s very existence. Instead, ask for more information or consider what you could have missed.
76 97 Things Every Programmer Should Know

Changing the status of a bug—e.g., Open to Closed—is a public statement of what you think of the bug. Taking the time to explain why you think the bug should be closed will save tedious hours spent later on justifying it to frus- trated managers and customers. Changing the priority of a bug is a similar public statement, and just because it’s trivial to you doesn’t mean it isn’t stop- ping someone else from using the product.
Don’t overload a bug’s fields for your own purposes. Adding “VITAL:” to the subject field may make it easier for you to sort the results of some report, but it will eventually be copied by others and inevitably mistyped, or will need to be removed for use in some other report. Use a new value or a new field instead, and document how the field is supposed to be used so other people don’t have to repeat themselves.
Make sure that everyone knows how to find the bugs that the team is supposed to be working on. This can usually be done using a public query with an obvi- ous name. Make sure everyone is using the same query, and don’t update this query without first informing the team that you’re changing what everyone is working on.
Finally, remember that a bug is not a standard unit of work any more than a line of code is a precise measurement of effort.
- How to Use a Bug Tracker
- How to Use a Bug Tracker
- how to debug a bug
- How to use a Ramdisk for Linux
- how to use a foreach in Qt
- A demo shows how to use TableLayout
- How to Use Java BigDecimal: A Tutorial
- When and how to use a ThreadLocal
- How to Use a QSqlQueryModel in QML
- How to use Git ,a magic software
- How to Write a Useful Bug Report
- How to write a good bug?
- How to write a good bug report
- How to use World Wind to give a presentation
- How to Use WinUSB to Communicate with a USB Device
- How to use maven to export a runnable jar
- How to use 'cp' command to exclude a specific directory?
- How to use a TControlCanvas in a component
- HighCharts使用
- The Guru Myth
- motor joint
- Hard Work Does Not Pay Off
- 黑马程序员——java面向对象思想
- How to Use a Bug Tracker
- CSU 1596 Dick.Z 的炉石赛 数学期望
- 缺陷的必然性
- 黑马程序员——java集合学习笔记
- 黑马程序员——java中数据类型包装类
- 判断一本书是否为好书的方法
- Sql Server2008——远程过程调用失败
- 为效益而测试
- Problem 2195 检查站点