Tips for efficient bug tracking
It was reported that in 1996, a US$ 1billion prototype, Ariane 5 rocket, of the European Space Agency, had to be destroyed less than a minute after launch, due to a bug in the on-board guidance computer program. Now, if you donât want your web application bringing down The Ford Motor Company in Michigan, read these few tips for successfully tracking bugs before launching your web applications.
 First and foremost â Never underestimate a bug!
 All bugs, be they small, obvious, minor or large, report them! If you go through a bug that is just too obvious that you are sure your developer will notice himself, let me tell you that there is no such thing as that. A fine bug report is one that contains each major and minor bug pointed out effectively enough to be reproduced and fixed.
  Secondly; donât expect your developer to untangle a series of bugs, itâs your job!
 In a bug report, put down the problems individually. One task per problem is how you should do it. If you are putting down three interrelated failures in a single bug, it becomes hard for your developer to separate, reproduce and fix them. Consequently, a bug or two or maybe ten are left in your program eventually destroying it.
  Also; just report the bugs, try not to be a quack by suggesting solutions!
Only mention the problem properly, in effective detail, instead for suggesting solutions. You might only be distracting your developer from the right path. Help your developer by submitting an adequate report of every bug crawling through the program.
    For effective results; use more words!
Whenever reporting a bug, write in detail. It becomes a lot easier for a developer to sort a bug out of the entire program code if the details of the problem are mentioned. For instance, in lieu of âcannot open pageâ if you report as:
âthis (URL) is not responding. On clicking the services icon, it reopens the home page (URL)â
Itâll specify the coding that needs to be modified and reproduction of bug will be easier.
  Be more helpful; add visual aid!
Use URLS, screenshots or error messages so it becomes easier for your developer to find the bug and fix it. It will increase the efficiency of bug tracking and fixing and eventually the pace of task.
  For extra surety; enhance the scrutiny in your work!
Write a bug report as a driver is advised to drive i.e. considering all other drivers blind and inexperienced. Key motive is to do your job perfectly instead of relying on others. Always consider that your developer will not be able to reproduce the âotherwise obvious bugâ. Itâs your job to track bugs for him, hence, add as much detail as you can. For example, mentioning what you expected to achieve and what you actually did on the web page, or how long should have taken for a certain webpage to load etc. Â
One important point to consider while tracking bugs is to never consider them as faults to be embarrassed about and try to hide. Instead, a tester should be more vigilant about thoroughly going through the program and filtering each and every bug out.
