Software Testing Tutorial: Writing Bug Reports; Mountain View, Silicon Valley, 2009

11 practical rules for writing professional grade bug reports. We teach these rules at Portnov Computer School (www.portnov.com) to career change students preparing to the Software Testing Career.

Here is the summary of BUG REPORTING RULES:

1. Do not assume developer knows less than you do about the application

2. Do not cite the rules – they know the rules, just talk about the problem itself

3. Report a bug immediately, do not postpone

4. Each “problem” has a story (each decision is a compromise) research before reporting

5. Do not assume all the companies have same approach to writing bug reports

6. Use technical terms, not “people off the street” language

7. Rule of WWW – What happened, Where it happened, under Which circumstances

8. Write one bug report for each fix to be verified

9. Bug report is not about perfect English

10. Bug reports are as concise as possible

11. Bug report should be as complete as possible

Related Blogs

  • Related Blogs on Bug
  • Related Blogs on computer
This entry was posted in Software Testing and tagged , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , . Bookmark the permalink.

Leave a Reply