How to prepare a effective bug report

How to prepare a effective bug report

After you complete your Software Testing, it is good practice to prepare an effective bug report. Fixing a bug depends on how effectively you report it. Below are some tips to write a good software bug report:
If you are doing manual Software Testing and reporting bugs withour the help of any tool, assign a unique number to each bug report. This will help to identify the bug record.Clearly mention the steps to reproduce the bug. Do not assume or skip any reproducing step.Be Specific and to the pointApart from these tips, below are some good practices:Report the problem immediatelyReproduce the bug atleast one more time before you report itTest the same bug occurrence on other similar modules of the applicationRead bug report before you submit it or send it.Never ever criticize any developer or attack any individual If you are using any Software Testing Management tool or any Bug reporting tool like Bugzilla or Test Director or Bughost or any other online bug tracking tool, then; the tool will automatically generate the bug report. If you are not using any tool, you may refer to the following template for your software bug report:
Name of Reporter:Email Id of Reporter:Version or Build: <Version or Build of the product>Module or component: <mention here the name of tested module or component>Platform / Operating System:Type of error: <coding error / design error / suggestion / UI / documentation / text error / hardware error >Priority:Severity:Status:Assigned to:Summary:Description: <mention here the steps to reproduce, expected result and actual result>

Blog Directory | Submit to Directories and Promote your Blogs