How to File a Bug: Difference between revisions
(Created page with " * [https://developer.mozilla.org/en-US/docs/Bug_writing_guidelines Bug writing guidelines] * [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bu...") |
(Removed dead links) |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
If you'd like to find bugs, QA has good instructions for [https://quality.mozilla.org/teams/web-qa/ exploratory and automated testing for Web QA]. Or try the main [https://quality.mozilla.org/docs/misc/how-can-i-help-test/ How to help test] page on QMO to find another bug hunting team! | |||
When you've found a bug, if you aren't experienced at writing bug reports, you should read through some of these guides. | |||
* [https://developer.mozilla.org/en-US/docs/Bug_writing_guidelines Bug writing guidelines] | * [https://developer.mozilla.org/en-US/docs/Bug_writing_guidelines Bug writing guidelines] Excellent information on writing good, useful bug reports. | ||
Before you file the bug, check to make sure it's new, by searching for similar bugs or bugs that have similar keywords in the summary. Consider also: is it really a bug? Might it be a support question answerable in the forums? | |||
Once your bug is filed, take another look at bugs in the same [https://bugzilla.mozilla.org/describecomponents.cgi?full=1 Product and Component] as your bug. Read through a few of them. You may be able to help sort them out -- and contribute to bug triage and management along with Mozilla's [[Bugmasters]]. | |||
Latest revision as of 21:39, 17 August 2017
If you'd like to find bugs, QA has good instructions for exploratory and automated testing for Web QA. Or try the main How to help test page on QMO to find another bug hunting team!
When you've found a bug, if you aren't experienced at writing bug reports, you should read through some of these guides.
- Bug writing guidelines Excellent information on writing good, useful bug reports.
Before you file the bug, check to make sure it's new, by searching for similar bugs or bugs that have similar keywords in the summary. Consider also: is it really a bug? Might it be a support question answerable in the forums?
Once your bug is filed, take another look at bugs in the same Product and Component as your bug. Read through a few of them. You may be able to help sort them out -- and contribute to bug triage and management along with Mozilla's Bugmasters.