Session-3

Question 1

Do not assume all the companies have same approach to writing bug reports

2. Rule of WWW – What happened, Where it happened, under Which circumstances
3. “Problem” bug report versus “Solution” bug report
4. Bug report is not about perfect English
5. Before reporting a bug, make sure that you are using the latest version of the AUT
6. Report a bug immediately, do not postpone
7. Make sure the bug is reproducible before reporting
8. Minimize number of steps-to-reproduce
9. Write one bug report for each fix to be verified
10. The difference between actual and expected results should be clear
11. Do not quote the violated rules or requirements (developers know them) – just talk about the problem itself
12. Do not assume developer knows less than you do about the application
13. Bug reports should be as concise as possible
14. Bug report should be as complete as possible
15. Attach screen shots, data files, logs to clarify the bug description
16. Each “problem” has a story (each decision is a compromise) research before reporting
17. Use technical terms, not “people off the street” language

Answer 1

q