The point of writing Problem Report is to get bugs fixed.
To write a fully effective report you must:
1. Explain how to reproduce the problem:
programmers dismiss reports of problems that they can’t see for themselves.
2, Analyze the error so you can describe it in a minimum number of steps.
Reports that contain unnecessary steps make the problem look less general than it is.They also confuse and intimidate the reader. A programmer is more likely to postpone dealing with a report that look long and involved.
3. Write a report that is complete, easy to understand, and non-antagonistic.
A report that confuses or irritates the programmer doesn’t motivate her to fix it.
No comments:
Post a Comment