QA: Quality assurance at Mozilla

  • Revision slug: QA
  • Revision title: QA
  • Revision id: 78513
  • Created:
  • Creator: Dria
  • Is current revision? No
  • Comment new topic page format

Revision Content

There are many things you can do to help out with the Mozilla project in the QA department, and all of them don't require being able to code. A few of them don't even require knowing any HTML or other web technologies. If you are interested in helping us out with testing and other QA activities, you should first read the Mozilla Quality Assurance and Helping with Quality Assurance pages.

Documentation

Bug Writing Guidelines
The more effectively a bug is reported, the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.
How to screen out duplicate bug reports
This is a guide to help you identify as many of the duplicate incoming bug reports as you can, as efficiently as possible. It's assumed that you are already comfortable with the basics of searching Bugzilla for duplicates.
How to find out if a bug has been previously reported
You can help to get more bugs fixed faster by checking the Bugzilla database before submitting your bug report, and not creating a duplicate report if the bug you found has been reported already.
How to use Regular Expressions when searching Bugzilla
This guide is designed to provide you with enough background knowledge and real-life examples to be able use the other text matching types mozilla offers (especially regular expressions) -- and that's how you'll get the experience.

View All...

Community

{{template.DiscussionList("dev-quality", "mozilla.dev.quality")}}

Tools

View All...

Related Topics

Developing Mozilla

Categories

Interwiki Language Links{{mediawiki.internal('zh-cn:质�?�?�?', "en")}}


{{ wiki.languages( { "fr": "fr/Assurance_qualit\u00e9" } ) }}

Revision Source

<p>
</p>
<div>
<p>There are many things you can do to help out with the Mozilla project in the QA department, and all of them don't require being able to code. A few of them don't even require knowing any HTML or other web technologies.  If you are interested in helping us out with testing and other QA activities, you should first read the <a class="external" href="http://www.mozilla.org/quality/">Mozilla Quality Assurance</a> and <a class="external" href="http://www.mozilla.org/quality/help/">Helping with Quality Assurance</a> pages.
</p>
</div>
<table class="topicpage-table">
<tbody><tr><td>
<h4 name="Documentation"> <a href="Special:Tags?tag=QA&amp;language=en">Documentation</a> </h4>
<dl><dt> <a href="en/Bug_Writing_Guidelines">Bug Writing Guidelines</a>
</dt><dd> <small>The more effectively a bug is reported, the more likely that an engineer will actually fix it.  By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.</small>
</dd></dl>
<dl><dt> <a class="external" href="http://www.mozilla.org/quality/help/screening-duplicates.html">How to screen out duplicate bug reports</a>
</dt><dd> <small>This is a guide to help you identify as many of the duplicate incoming bug reports as you can, as efficiently as possible. It's assumed that you are already comfortable with the basics of searching Bugzilla for duplicates.</small>
</dd></dl>
<dl><dt> <a class="external" href="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html">How to find out if a bug has been previously reported</a>
</dt><dd> <small>You can help to get more bugs fixed faster by checking the Bugzilla database before submitting your bug report, and not creating a duplicate report if the bug you found has been reported already.</small>
</dd></dl>
<dl><dt> <a class="external" href="http://www.mozilla.org/bugs/text-searching.html">How to use Regular Expressions when searching Bugzilla</a>
</dt><dd> <small>This guide is designed to provide you with enough background knowledge and real-life examples to be able use the other text matching types mozilla offers (especially regular expressions) -- and that's how you'll get the experience.</small>
</dd></dl>
<p><span class="alllinks"><a href="Special:Tags?tag=QA&amp;language=en">View All...</a></span>
</p>
</td>
<td>
<h4 name="Community"> Community </h4>
<ul><li> <a class="external" href="http://weblogs.mozillazine.org/qa/">Mozilla Quality Assurance Blog</a>
</li><li> View Mozilla forums...
</li></ul>
<p>{{template.DiscussionList("dev-quality", "mozilla.dev.quality")}}
</p>
<ul><li> <a class="external" href="irc://irc.mozilla.org/qa">#qa on irc.mozilla.org</a>
</li><li> <a class="external" href="irc://irc.mozilla.org/bugs">#bugs on irc.mozilla.org</a>
</li><li> <a class="external" href="irc://irc.mozilla.org/smoketest">#smoketest on irc.mozilla.org</a>
</li><li> <a href="en/QA/Community">Other community links...</a>
</li></ul>
<h4 name="Tools"> Tools </h4>
<ul><li> <a class="external" href="https://bugzilla.mozilla.org/enter_bug.cgi?format=guided">Bugzilla</a>
</li><li> <a class="external" href="http://litmus.mozilla.org/">Litmus</a>
</li><li> <a href="en/QA/Stress_Testing">Stress Testing</a>
</li></ul>
<p><span class="alllinks"><a href="Special:Tags?tag=QA:Tools&amp;language=en">View All...</a></span>
</p>
<h4 name="Related_Topics"> Related Topics </h4>
<dl><dd> <a href="en/Developing_Mozilla">Developing Mozilla</a>
</dd></dl>
</td></tr></tbody></table>
<p><span class="comment">Categories</span>
</p><p><span class="comment">Interwiki Language Links</span>{{mediawiki.internal('zh-cn:质�?�?�?', "en")}}
</p><p><br>
</p>{{ wiki.languages( { "fr": "fr/Assurance_qualit\u00e9" } ) }}
Revert to this revision