How to write a good bug report
1) Report the problem immediately:
Well If you found any bugs while testing the website or web applications, do not wait to write detail bug report later. write the bug report immediately as soon as possible. This will may ensure a good and reproducible bug report. If you decide to write the bug report later on then chances are high to miss the important steps in your report.so always be fast on your work
2) Reproduce the bug three/four times before writing a bug report:
Your
bugs should always be reproducible. Make sure your steps are most robust enough to
reproduce the bugs without any ambiguity. If your bugs is not reproducible
every time you can still file a bug mentioning the periodic nature of
the bug.
3) Test the same bugs occurrence on other similar module
Sometimes developer use same code for different similar modules. So chances are more higher that bug in one module can occurs in other similar modules as well. Even you can try to find more severe version of the bug you found.
4) Write a good bugs summary for Bug reports
Bugs summary will help developers/programmers to quickly analyze the bugs nature. Poor
quality report will unnecessarily increases the development and testing
time. Communicate well through your bug report summary. Keep in mind bug
summary is used as a reference to search the bug in bug inventory.
5) Read bugs report before hitting Submit button
Read all sentences, wording, steps used in bug reports. See if any sentence is creating ambiguity that can leads to misinterpretation. Misleading words or sentences should be avoided in order to have a clear bug reports.
6) Do not use Abusive languages on bug report
It is nice that you did a good work and found a bug but do not use this credit for criticizing developer/programmer or to attack any individuals.
Conclusion
No doubt that your bugs report should be a high quality documents. Focus on writing good bug reports, spend some time on this tasks because this is main communication point between tester,programmer, developer and manager. Managers should make aware to their team that writing a good bug report is primary responsibility of any tester. Your efforts should towards writing good bug report will not only save company resources but also create a good relationship between you and developers/programmers
For better productivity write a better bug report
1) Report the problem immediately:
Well If you found any bugs while testing the website or web applications, do not wait to write detail bug report later. write the bug report immediately as soon as possible. This will may ensure a good and reproducible bug report. If you decide to write the bug report later on then chances are high to miss the important steps in your report.so always be fast on your work
2) Reproduce the bug three/four times before writing a bug report:
3) Test the same bugs occurrence on other similar module
Sometimes developer use same code for different similar modules. So chances are more higher that bug in one module can occurs in other similar modules as well. Even you can try to find more severe version of the bug you found.
4) Write a good bugs summary for Bug reports
Bugs summary will help developers/programmers to quickly analyze the bugs nature. Poor
quality report will unnecessarily increases the development and testing
time. Communicate well through your bug report summary. Keep in mind bug
summary is used as a reference to search the bug in bug inventory.5) Read bugs report before hitting Submit button
Read all sentences, wording, steps used in bug reports. See if any sentence is creating ambiguity that can leads to misinterpretation. Misleading words or sentences should be avoided in order to have a clear bug reports.
6) Do not use Abusive languages on bug report
It is nice that you did a good work and found a bug but do not use this credit for criticizing developer/programmer or to attack any individuals.
Conclusion
No doubt that your bugs report should be a high quality documents. Focus on writing good bug reports, spend some time on this tasks because this is main communication point between tester,programmer, developer and manager. Managers should make aware to their team that writing a good bug report is primary responsibility of any tester. Your efforts should towards writing good bug report will not only save company resources but also create a good relationship between you and developers/programmers
For better productivity write a better bug report
Post a Comment
Thank you for visiting Afridi's Technoworld