How to log software testing defects better? What are the tips for QA defect logging?

Test defects are logged in by the testers, and the get fixed by the developers. In between the logging and fixing cycle, a few defects leak out, slip out or die before getting fixed. Why? Because the defect reports were not written effectively and failed in making their point. So how can a software tester log defects in a better way so as to ensure that every defect reported, gets fixed? Read on for tips and steps that a software QA tester can follow to ensure this.

• Ensure the defect is constantly reproducing thrice on your system. This will ensure that the software tester can got all his steps right. Quite often a software tester is not able to reproduce the behavior on his own system, because he is not aware of what steps he followed to come across that anomaly.
• Ensure that you accurately depict the system behavior, the expected output and the actual output that was seen to constitute the defect. Clear and simple language should be used here.
• Desist from finger-pointing or painting the system or developer in bad terms. Just report the system anomaly in a neutral tone.
• Ensure that you report all the necessary information such as Build on which the error was seen, the OS, the browser type and version etc. Basically the developer should get all the information about the test environment in which the error was seen.
• Ensure that you report each and every step that need to be followed in enough detail. Using your steps should allow any developer or tester to reproduce the erroneous system behavior.
• Attach snapshots of the error screen, log files or any other output artifacts to support your claim of error in the system. A developer will find it hard to refute your defect when given evidence to substantiate it.
• Ensure the defect title is short and succint. It should clearly summarize the defect and its behavior in as few words as possible.
• Ensure that the defect priority and defect severity are correctly determined. Many a times the developer will refute your choosen values in order to lessen his work, but you should be firm with this, and explain him why you have choosen so and so priority / severity for this.

Following these steps will ensure that minimum number of your defects will be reported as not-reproducable by the developers, and your reported defects will have a high fix rate.