For developer defects are an integral part of the software development life cycle. The more efficient a bug report is the more likely the defect will be fixed. Reporting a bug is no rocket science but to become a pro in testing you need to achieve this skill.
Following some tips which hopefully help you to master this skill.
REPORT THE PROBLEM IMMEDIATELY
Don’t wait with writing bug reports because you could miss important details. If you found any defect while testing, report it immediately. The earlier the bug gets reported the sooner developers and management are aware of them and can start dealing with it.
CLEAR SUMMARY
Keep it short. It is very important to gasp the essence of the defect from the summary. Also it will help to find it through the large database for assigning to the correct developer. Remember “It doesn’t work” is not a proper description.
ONE DEFECT PER REPORT
A single bug in a report can help to avoid confusion and duplication. If you describe too many defects some may be overlooked. So stick to one: no more, no less.
REPRODUCE THE BUG
Make sure your steps lead to reproducing the bug without uncertainty. The defect should be reproducible. In case you are unable to reproduce it 100% but know that there is something fishy, gather as many information as possible which may helpful for the developer for further investigation.
TEST DEFECT IN SIMILAR MODULES
In most projects the developers use the same code for different modules. There is a high chance that defect in one module also occurs in other similar modules.
READ BUG REPORT CAREFULLY
Try to read your bug report thoughtfully before submitting it. Make sure all phrases are written in a clear and understandable way to avoid misunderstandings.
DON’T BE RUDE
You did a really good job in finding the defect but stay polite and don’t criticize the developer this way.
Most of the testers don’t like to write reports thinking it is a waste of their time. But a bug report is a very important document and needs to be written properly as it connects tester, developer and manager. Writing a good bug reports helps your company to save resources as well as creates a good relationship between tester and developer.