Effective Logging of Bugs

July 4, 2011 - PRLog -- Let’s talk about the situation when you find a bug. Then you should notice what the reason of the problem was. This may sound evident, but it is the most significant detail and bears repeating.
Being able to break steps down logically and to recall in a step-by-step manner what led to the manifestation of the software bug is way to success.
So the first thing you should do before paying attention to any bug is to find the bug-tracking database to see if the issue has already been identified. If the software bug has already been entered, it may still be active, but not in the compelling script that you have identified. You should add that information to the database, and bring it to the attention of the developer or the test lead. The bug might be closed and identified as one that management is convenient navigation the product with, or something for which there is no fix.
To log effective repro steps:
1.   Come across the straightest way to trigger the bug.
2.   Clearly report this in your steps.
3.   Test the steps second time to be sure that you didn't undertake something wrong.
4.   Check, using other machines, if possible, to verify that the bug is reproducible or is dependent on the conditions you believe it is.
You should know that entering duplicate bugs in the database is a software tester http://qatestlab.com/company/our-team/ error. When it happens, it means that you are a sloppy tester. However, it can also be a sign that the original bug information that was entered was written badly and with useless detail. It is imperative that a clear, linear, reproducible set of steps be included in the log information. It is good if you can only get the bug to appear half the time that the steps are conducted; don’t forget to describe that in the report. Just imagine that you are a detective. You need to gather up all the clues to hand over to the developers so they can identify the trouble.
For example, you can say that the software you are working on is a Web community. The software bug http://qatestlab.com/services/sample-deliverables/bug-rep... you identify is that when you log in nothing happens. Here is an ineffectual way to log this new entry into the database:
I can't get the community to log me in. I type in my name and nothing happens.
From this explanation, it would be impossible to recognize what exactly you were doing. From an outsider's point of view, you could be doing anything.
Here is a more efficient entry:
I am unable to log in to the community.
1.   Open IE 5.5 on Windows 2000.
2.   Enter in the community URL in the location bar. Hit Enter.
3.   In the Login: text box, enter the name user01.
4.   Tab to the Password: text box and input the password 123.
5.   Click LOGIN to send the information.
Result: Nothing happens, but the IE icon keeps spinning/waving.
In this case anybody could look at the problem and see what happened. You could also make this entry better if you provided some other parts of information.

# # #

QATestLab is independent, offshore software testing company located in Kiev, Ukraine. QATestLab performs testing of products on each stage of software development cycle.