It is essential that you report defects effectively so that time and effort is not unnecessarily wasted in trying to understand and reproduce the defect. Here are some guidelines:

i. Be specific:

• Specify the exact action: Do not say something like ‗Select Button B‘.

• Do you mean 'Click Button B‘ or 'Press ALT+B‘ or 'Focus on Button B and click ENTER‘.

• In case of multiple paths, mention the exact path you followed: Do not say something like ―If you do 'A and X‘ or 'B and Y‘ or 'C and Z‘, you get D.‖ Understanding all the paths at once will be difficult. Instead, say ―Do 'A and X‘ and you get D.‖ You can, of course, mention elsewhere in the report that ―D can also be got if you do 'B and Y‘ or 'C and Z‘.‖

• Do not use vague pronouns: Do not say something like ―In Application A, open X, Y, and Z, and then close it.‖ What does the 'it‘ stand for? 'Z‘ or, 'Y‘, or 'X‘ or 'Application A‘?‖

ii. Be detailed:

• Provide more information (not less). In other words, do not be lazy.

• Developers may or may not use all the information you provide but they sure do not want to beg you for any information you have missed.

iii. Be objective:

• Do not make subjective statements like ―This is a lousy application‖ or ―You fixed it real bad.‖

• Stick to the facts and avoid the emotions.

iv. Reproduce the defect:

• Do not be impatient and file a defect report as soon as you uncover a defect. Replicate it at least once more to be sure.

v. Review the report:

• Do not hit ‗Submit‘ as soon as you write the report.

• Review it at least once.

• Remove any typing errors.