Guidelines for writing good and effective Defect Entry.

1. Keep the Defect Summary concise. The defect summary should be very concise and to the point, developer should not need to scroll through the synopsis. For example, “Customer data import fails when .zip file is selected”. Also it is a good practice to indicate the affected area by putting...

×