撰寫好的Bug Report之技巧與秘訣

How to write a good bug report? Tips and Tricks
http://jaanujeeva.blogspot.com/2009/01/how-to-write-good-bug-report-tips-and.html

最近老闆發現某個product, 有20%~30%的bug被reject. 中間的原因可能很多, 但是也突顯了bug report 的重要性. 如果你能產生有效的bug report, 能準確提供問題所在之處, 這樣才能讓所有人都達到win win的地步.

這裡找到一篇bug report 的經驗談, 大家享用吧!!

1. 為什麼要產生好的bug report
- 如果你的bug report能有效率的指出問題所在, RD越有機會能更解決它
- Cem Kaner.曾說“The point of writing problem report(bug report) is to get bugs fixed”
- 如果QA沒有辦法產生出正確的bug report, RD最後有可能說這bug是沒有問題的, 因而reject它. 這將會導致QA的士氣其受損, 甚至防衛心理或對立心理而升高


2. 好的Bug Report應該具備有怎樣的特質呢?
(1) Having clearly specified bug number:
- Always assign a unique number to each bug report.
- This will help to identify the bug record.
- Note the number and brief description of each bug you reported.

(2) Reproducible:
- If your bug is not reproducible it will never get fixed.
- You should clearly mention the steps to reproduce the bug.
- Do not assume or skip any reproducing step.
- Step by step described bug problem is easy to reproduce and fix.

(3) Be Specific:
- Do not write a essay about the problem.
- Be Specific and to the point.
- Try to summarize the problem in minimum words yet in effective way.
- Do not combine multiple problems even they seem to be similar.
- Write different reports for each problem.

一些能幫助你寫好bug report的小技巧
(1) Report the problem immediately:
- If you found any bug while testing, do not wait to write detail bug report later. Instead write the bug report immediately.
- This will ensure a good and reproducible bug report.
-If you decide to write the bug report later on then chances are high to miss the important steps in your report.

(2) Reproduce the bug three times before writing bug report:
- Your bug should be reproducible.
- Make sure your steps are robust enough to reproduce the bug without any ambiguity.
- If your bug is not reproducible every time you can still file a bug mentioning the periodic nature of the bug.

(3) Test the same bug occurrence on other similar module:
- Sometimes developer use same code for different similar modules.
- So chances are high that bug in one module can occur in other similar modules as well.
- Even you can try to find more severe version of the bug you found.

(4) Write a good bug summary:
- Bug summary will help developers to quickly analyze the bug nature.
- Poor quality report will unnecessarily increase the development and testing time.
- Communicate well through your bug report summary. Keep in mind bug summary is used as a reference to search the bug in bug inventory.

(5) Read bug report before hitting Submit button:
- Read all sentences, wording, steps used in bug report.
- See if any sentence is creating ambiguity that can lead to misinterpretation.
- Misleading words or sentences should be avoided in order to have a clear bug report.

(6) Do not use Abusive language:
- It’s nice that you did a good work and found a bug but do not use this credit for criticizing developer or to attack any individual.
- Conclusion: No doubt that your bug report should be a high quality document.
- Focus on writing good bug reports, spend some time on this task because this is main communication point between tester, developer and manager.
- Mangers should make aware to their team that writing a good bug report is primary responsibility of any tester.
- Your efforts towards writing good bug report will not only save company resources but also create a good relationship between you and developers.
arrow
arrow
    全站熱搜

    kojenchieh 發表在 痞客邦 留言(0) 人氣()