Software Testing, QA

example of bug report

The template of the bug report depends on the bug tracking system you use. Usually the bug report should contain the following fields:

  • unique identifier
  • build version
  • summary
  • description
  • step to reproduction
  • reproduction (always, sometimes)
  • severity
  • priority
  • symptom

As soon as a bug has been found, it must be reported because you can forget about the bug. Do not prepare the report on a paper (you can lose it) and log the report to the bug tracking system. These are simple rules but many testers neglect them and many bugs have been left unfixed.

Read the rest of this entry »


Comments on: "How to create a good bug report" (5)

  1. Eric Rayburn said:

    Eric Rayburn posted:

    The article is an excellent source of informing the tester or the many types of way to identify and fix bug problems. I intend I incorporating these tactics in my work.

  2. Natalya Bosatskaya said:

    @Eric Rayburn

    Thank you! I’m glad that you like the article.

  3. Hello, this is a good write-up. You receive my vote for How to create a good bug report Practical Tips on Software Testing and also I am going to bookmark this blog now.

    • Natalya Bosatskaya said:


      Thanks 🙂 We have already prepared a few interesting articles, and soon we are going to publish them.

  4. Hello,I like to read more on this field. Thank you for publishing How to create a good bug report Practical Tips on Software Testing.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: