Gecko BugAThon

  • Revision slug: Gecko_BugAThon
  • Revision title: Gecko BugAThon
  • Revision id: 65551
  • Created:
  • Creator: Gerv
  • Is current revision? No
  • Comment 137 words added, 53 words removed

Revision Content

Do you care about Web standards? Do you hate working around browser bugs? Don't just stand there - with engineers bleeding by the side of the road, are you going to be the Pharisee or the Good Samaritan?

You can help, and you don't need to be a C++ programmer! Simplifying bug reports to the simplest possible test case doesn't take too long per bug, but when you've got as many bugs as we do, the time really adds up. And every hour Gecko engineers spend decomposing bug reports is an hour they can't spend on FIXING bugs. The more bugs that are simplified, the faster Gecko engineers can fix them, and the fewer bugs there'll be!

Writing a testcase is also the best and most productive way to vote for a bug. Overworked engineers tend to focus on bugs with testcases. If a bug bothers you, why it does still not have a testcase?

What Is A Test Case?

A simplified test case means the simplest possible Web page that still reproduces the bug. If you remove any more characters from the file of the simplified test case, you no longer see the bug. You can find out how to make them at Reducing_testcases.

Finding The Bugs

Bugs which definitely need a testcase are flagged with the testcase-wanted keyword (search). If there are none of those, then try the following components. (Why not adopt one?)

Document Navigation
DOM
DOM: Core & HTML
DOM: CSS Object Model
DOM: Events
DOM: Mozilla Extensions
DOM: Other
DOM: Traversal-Range
DOM: Validation
Drag and Drop
Editor
Event Handling
Find Backend
General
GFX
GFX: Thebes
HTML: Form Submission
HTML: Parser
JavaScript Engine
Layout
Layout: Block and Inline
Layout: Canvas
Layout: Floats
Layout: Form Controls
Layout: HTML Frames
Layout: Images
Layout: R & A Pos
Layout: Tables
Layout: Text
Layout: View Rendering
MathML
Print Preview
Printing: Output
Selection
Serializers
Style System (CSS)
SVG
XBL
XML
XSLT
XUL

Procedure

Find a bug, create a reduced testcase and attach it to the bug. When you've done that, change the testcase-wanted keyword to a testcase keyword, and move on to the next bug. If you don't have sufficient Bugzilla permissions to add keywords or attachments,  mail Gerv to obtain additional permissions.

Rewards

This is the good bit. Each time you make a testcase, bookmark the bug. When you've got to 20, email the list to XXXWHO? to receive a free Firefox plushie!

Revision Source

<p>Do you care about Web standards? Do you hate working around browser bugs? Don't just stand there - with engineers bleeding by the side of the road, are you going to be the Pharisee or the Good Samaritan?</p>
<p>You can help, and you don't need to be a C++ programmer! Simplifying bug reports to the simplest possible test case doesn't take too long per bug, but when you've got as many bugs as we do, the time really adds up. And every hour Gecko engineers spend decomposing bug reports is an hour they can't spend on FIXING bugs. The more bugs that are simplified, the faster Gecko engineers can fix them, and the fewer bugs there'll be!</p>
<p>Writing a testcase is also the best and most productive way to vote for a bug. Overworked engineers tend to focus on bugs with testcases. If a bug bothers you, why it does still not have a testcase?</p>
<h3>What Is A Test Case?</h3>
<p>A simplified test case means the simplest possible Web page that still reproduces the bug. If you remove any more characters from the file of the simplified test case, you no longer see the bug. You can find out how to make them at <a href="/en/Reducing_testcases" title="en/Reducing_testcases">Reducing_testcases</a>.</p>
<h3>Finding The Bugs</h3>
<p>Bugs which definitely need a testcase are flagged with the <code>testcase-wanted</code> keyword (search). If there are none of those, then try the following components. (Why not adopt one?)</p>
<p><a class="link-https" href="https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&amp;keywords=testcase&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=blocker&amp;bug_severity=critical&amp;bug_severity=major&amp;bug_severity=normal&amp;bug_severity=minor&amp;cmdtype=doit&amp;component=Document%20Navigation" title="https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&amp;keywords=testcase&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_severity=blocker&amp;bug_severity=critical&amp;bug_severity=major&amp;bug_severity=normal&amp;bug_severity=minor&amp;cmdtype=doit&amp;component=Document Navigation">Document Navigation</a><br>
DOM<br>
DOM: Core &amp; HTML<br>
DOM: CSS Object Model<br>
DOM: Events<br>
DOM: Mozilla Extensions<br>
DOM: Other<br>
DOM: Traversal-Range<br>
DOM: Validation<br>
Drag and Drop<br>
Editor<br>
Event Handling<br>
Find Backend<br>
General<br>
GFX<br>
GFX: Thebes<br>
HTML: Form Submission<br>
HTML: Parser<br>
JavaScript Engine<br>
Layout<br>
Layout: Block and Inline<br>
Layout: Canvas<br>
Layout: Floats<br>
Layout: Form Controls<br>
Layout: HTML Frames<br>
Layout: Images<br>
Layout: R &amp; A Pos<br>
Layout: Tables<br>
Layout: Text<br>
Layout: View Rendering<br>
MathML<br>
Print Preview<br>
Printing: Output<br>
Selection<br>
Serializers<br>
Style System (CSS)<br>
SVG<br>
XBL<br>
XML<br>
XSLT<br>
XUL</p>
<h3>Procedure</h3>
<p>Find a bug, create a reduced testcase and attach it to the bug. When you've done that, change the <code>testcase-wanted</code> keyword to a <code>testcase</code> keyword, and move on to the next bug. If you don't have sufficient Bugzilla permissions to add keywords or attachments,  <a class="external" href="http://www.gerv.net/hacking/before-you-mail-gerv.html" title="http://www.gerv.net/hacking/before-you-mail-gerv.html">mail Gerv</a> to obtain additional permissions.</p>
<h3>Rewards</h3>
<p>This is the good bit. Each time you make a testcase, bookmark the bug. When you've got to 20, email the list to XXXWHO? to receive a free <a class="external" href="http://intlstore.mozilla.org/product%20info.php?products%20id=122" title="http://intlstore.mozilla.org/product info.php?products id=122">Firefox plushie</a>!</p>
Revert to this revision