Mallow's Blog

Bug Reporting Guide

Bug Reporting

Bug Reporting is the process of reporting a bug to the corresponding developer to fix it. Testers can report a bug using bug tracking tools. Need to fill the subsequent fields while raising a bug.

  • Project Name
  • Bug Summary
  • Description
    –  Reproducible steps
    – Actual Result
    – Expected Result
  • Bug Priority
  • Bug Severity
  • Assigned To
  • Status
  • Reporter
  • Affects Version
  • Environment
  • Component/Module
  • Attachments
  • Test case link

Severity Vs Priority

Most of the people do not know the difference of Severity & Priority. Here let’s get to know the difference.


  • Priority is how quickly it must be resolved
  • Priority status is set based on the client requirement
  • Status can be (Low, Normal, High, Urgent, Immediate)


– Severity of a software bug is predicted on the percentage of the bug impact on the operation of the system
– Status can be (Blocker, Critical, Major, Minor, Trivial)

Why Need a Good Bug Report?

If the bug is reported effectively then chances are very high that it will get fixed soon or else Developer need to communicate with the tester who has raised the bug. So fixing a bug depends on how effectively We have reported it.

Qualities of a Good Bug Report

  • Reproducible – Include reproducible steps.
  • Be Specific – Bug / Defect summary as well as description should be understandable
  • Need to add the bug related screenshots

Tips to write down a Good Bug Report

  • Report the problem immediately by using a bug reporting tool.
  • Try to reproduce the bug twice before reporting in the bug tracking tool.
  • Test an equivalent bug occurrence on other similar module also.
  • Bug summary that provides a short description about the bug.

Bug life cycle stages

  • Open – A bug raised by QA team and yet to be fixed by developer
  • In Progress – Developer started fixing the bug
  • Deferred –  Move the bug fixes to next/ future release
  • Duplicate – A Bug raised twice .
  • Fixed – Bug has been fixed by developer and QA team has to verify
  • Reopened – When a bug resolved by developer reproduces again
  • Closed – If bug is verified by the QA team and it is fixed then QA can mark bug as ‘Closed’ or a bug can be closed when the defect is duplicate

Risks of not using Bug Tracker

  • Important issues will be lost
  • Project teams waste an excessive amount of  time in figuring out the stability of the  project
  • Client do not have the idea about the progress of bug fixing activity
  • Developer will not be aware if an issue is not reported
  • Getting bug status reports takes too long

Needs of Bug Tracker

  • Deliver the high quality products
  • Improve customer satisfaction
  • The cost of  development is low 

Bug Tracking Tools

There are tons of bug tracking tools are available for software testing. Here are the few,

  • HP ALM
  • JIRA
  • Mantis
  • Trac
  • Redmine
  • FogBugz
  • BugNet

Lets deliver the bug free products to the customer !!!!!

Testing Team,
Mallow Technologies.

Leave a Comment

Your email address will not be published. Required fields are marked *