Defect Management

10 Tips to write a complete Bug Report in Software Testing

Software Defect

In previous article we discussed about Defect Life Cycle. Now we will see why it is essential to write a qualitative Bug Report. Each Bug tracking tool have its own format of Bug report but there are mandatory sections will always be there.

Effective bug report leads to higher rate of resolving defects.

Let’s take an example of Live Scenario to understand why meaningful report is so necessary.

– During the testing of a functionality Tester has found one defect. Now he reports that defect with poorly written insufficient information and assigns to one of the developer. The developer not knowing anything about the behavior of this defect tries to understand and reproduce the same on his machine. As the steps are not clearly defined in the defect, he fails to reproduce it and therefor he assigns the defect back to Tester with the status “Not A Defect” or “Can Not Reproduce“.

– Now Tester has to make him understand the behavior of the defect. He will do it by either updating the description of the defect report or he will just go at developer’s desk and reproduce the defect on his machine.

– Imagine the time has spent on single issue just to re-produce on developer’s machine. If the Tester would have provided the detailed steps and summary in the first place than they could have avoided wasting extra time spent on re-work.

Below mentioned are some tips for writing an effective Bug Report :

1) Defect Title – Meaningful & Self-explanatory

Title of any defect should be written in such way that anyone can get high level idea of the defect’s nature just by reading these one or two lines.

Sometimes a good title gives everything you need to know about the defect and yes it saves much of your time.

2) Don’t forget to mention Precondition (If Applicable)

Some defects are not straight forward to re-produce. You have to perform some steps / scenarios before executing steps to re-produce the defect. In such cases, developer won’t be able to reproduce the defect if precondition is missing.

Example : In an e-commerce website you find a defect on the discount applied feature. Now let’s say this defect is re-producible only for few categories of product.

So while writing bug report you need to mention all those categories in the Precondition.

3) Steps To Reproduce the Defect – Mention all steps in detail (Without Fail)

Starting from accessing URL of the application, you must mention all the steps and conditions leading to occurrence of the defect. Do not write as a summary, it’s boring to read and less informative. Keep each condition / step in separate point with proper numbering.

4) Do not worry about Defect Count. Keep each defect discrete

Combining multiple defects into single one will surely save your time while reporting but later it will lead to the confusion. let’s say you have combined 3 defects (occurring on the same page) into single one. Now developer has resolved one of the issue but remaining two are still open. You can’t close the defect until any single issue mentioned is not resolved.

In some scenarios, long discussions happen on the defect through comments. In such cases, managing multiple defects in single report may lead to mess.

5) Do not introduce Business Scenarios, Just pass suggestions

While testing an application you might feel some scenarios / business flows should be added or removed (ofcource for the betterment). Do not raise them as the defects, but yes such cases can be reported as Suggestions. Just pass the information and let the Business do the judgement.

6) Grammatical Mistakes – Avoid

Be very precise while writing a Bug report. Try avoiding fancy words. Keep it simple and more understandable. You don’t want the developer to get confused and come to you for explanation. There are many Spell check add-on for each browsers which can help you in avoiding spelling mistakes.

7) Severity & Priority of the Defect

Each and every defect must be having appropriate value of Severity and Priority. Severity decides the impact of the defect on the application & Priority gives information on how quickly the defect should be fixed. Developers will focus on resolving defects having Highest Priority and severity first.

8) Dependency on other defects

Some defects are having dependency on other issues, meaning you can not verify and close the defect unless and until other one is not resolved. You will face situations like: A defect is assigned to you marked as Fixed, but you are unable to verify that because of the step you need to perform to check itself is having an issue. In such cases, keep the defect “On Hold for verification” and link with the dependent Bug number. Don’t forget to provide proper comment like : “Issue#1 is dependent on Issue#2. Once Issue#2 is resolved and assigned for testing, QA person will be able to verify and close Issue#1”.

9) Nature of Occurrence

Some defects occur in random manner. There are not exact steps to reproduce and you can’t track the occurrence behavior as well. For such defects you can mention something like this :

“This defect is re-producible on random basis with the ratio of 4-5 / 10 times.”

10) Do not forget to mention Build number / Version # / Server details in Bug Report

During the software testing life cycle, your project goes through different servers : Dev Server, QA Server, Pre-Production, Live etc. So whenever you are reporting any defect, mentioning these information is must :

– On which Build version you are doing testing and Defect is reported
– On which Server issue is found, resolved and closed.

Other than these scenarios listed above, if you want to share anything please let us know. Thank You!!

Share This Article :


  1. QA

    Brilliant steps to Bug reporting and notes for all test analyst.
    Keep updating us with such grateful ideas fo beginners.
    Thank you.

  2. Oh my goodness! Amazing article dude! Thank you so much, However I am
    experiencing difficulties with your RSS.
    I don’t know the reason why I can’t subscribe to it. Is there
    anybody else getting the same RSS problems? Anybody who knows the
    answer will you kindly respond? Thanks!!

  3. you’re truly a good webmaster. The site loading velocity is incredible.
    It sort of feels that you are doing any distinctive trick.

    Furthermore, The contents are masterwork. you have performed a fantastic activity
    in this matter!

  4. Excellent post! We are linking to this particular particularly great
    article on our website. Continue the best writing.

  5. Hello, I love reading all of your article. I wanted to write down a little comment to aid you.

  6. Hello to all, the contents present at this web page are really
    remarkable for people knowledge, well, keep up the nice work fellows.

  7. Pretty great post. I simply found your blog and wished to say that I’ve really loved browsing your blog
    posts. All things considered I am going to be subscribing to your feed and I am hoping you write again soon!

  8. Hi to every body, it’s my first visit of this weblog; this website carries remarkable and really excellent stuff in favor of visitors.

  9. Anonymous

    Amazing! Its really awesome piece of writing, I have got much clear idea about from this article.

  10. Hello I am so delighted I found your site, I really found you by accident, while I was browsing on Askjeeve for something else, Regardless I am here now and would just like to say thanks a lot for an incredible post and a all round exciting
    blog (I also love the theme/design), I don’t have time to read through it all at the minute but I have book-marked it and also added in your RSS feeds, so when I have time I will be back to read much more, Please do keep up the superb b.

  11. Thank’s great post.

  12. m88

    This website was… how do you say it? Relevant!!

    Finally I have found something that helped me. Cheers!

  13. I’m very happy to find this page. I wanted to thank you for ones time for this particularly
    fantastic read!! I definitely enjoyed every little bit of it and I
    have you book marked to see new information in your site.

  14. Hello there, just became aware of your blog through Google, and found that it’s truly informative.
    I’m gonna watch out for brussels. I will appreciate if you continue this in future.
    A lot of people will be benefited from your writing.

  15. florentina Wyant

    I seriously love your website.. Very nice colors & theme.

    Did you build this web site yourself? Please reply back as I’m hoping to create my own site and would
    like to know where you got this from or what the theme is called.

  16. Martins

    Brilliant steps to Bug reporting and note for all test analyst and technical tester.
    Keep the good work going.
    Will share will Team members

  17. I was recommended this website by my cousin. I am not sure whether this post is written by him as nobody else know such detailed about my trouble.
    You are wonderful! Thanks!

  18. Jim

    What’s up, I check your new stuff daily. Your writing style is awesome,
    keep doing what you’re doing!

    • Rishil Bhatt

      Hey Jim, Thank You for this comment. Many more such articles will be published gradually. Stay Connected.

      Thanks Again !!

  19. I am sure this post has touched all the internet users, its
    really really pleasant paragraph on building up new

    • Rishil Bhatt

      Hello Chrinstine,

      Thank You for your comment. Glad you liked it.

Leave a Reply