Flock | the social web browser

Verifying A Bug

Contents

[edit] What's bug verification? Why would I do it?

Bug verification is an ideal way to get involved with Flock. When you verify a bug, you're providing the final word on whether a Flock developer fixed that bug correctly or not.

Sometimes, the developer may have missed a small detail, or even broken something else while fixing the bug. And sometimes, the developer just misunderstood the bug. One industry statistic suggests that as many as 20 percent of fixed bugs aren't fixed correctly. That's why at Flock, we only consider a bug truly fixed after a tester has verified the fix.

Bug verification is a great way to become acquainted with open source projects and software development. You don't have to program, you can do as much (or as little) as you want, and you have the opportunity to exercise your creativity and ingenuity. In fact, it's one of the ways Blake Ross (who later co-created Firefox) originally became involved with Mozilla.

And that's where you, too, can come in.

[edit] How to verify a fixed bug

To get started verifying a bug, you'll first need the most recent (topmost) testing build of Flock. Download it here.

Then, search Bugzilla for a bug that you think you can verify: List of fixed bugs needing verification

How do you know which bug to verify? Pick one that you understand - many bugs include step-by-step instructions so you can reproduce the problem. Other Flock bugs were written by developers exclusively for other developers. Those often don't make much sense to anyone else but the author and their immediate peers.

Then, you can verify it by asking these four questions:

  1. Is this bug, as described, fixed? Using a current Flock build, can you reproduce the problem? Sometimes a developer will fix a broad problem area and mark all the bugs in that area fixed. Sometimes, they're not. Sometimes, bug reporters also mention several bugs in a single bug report; be sure to read all the way to the end!
  2. Could remaining "corner cases" exist that the developer may have missed? Bugs often exist in clusters. Where you find a bug, you'll often find more. Are there other bugs like the one you're verifying that the developer may have missed? Get creative and play around -- this is the fun part!
  3. Do bugs marked as a duplicate of this bug still contain active problems? Sometimes, developers (and testers) erroneously mark one bug as a duplicate of another. You can avoid the loss of relevant bug reports by checking a bug's duplicates when you verify the bug.
  4. (Bonus Points) Did the bug fix create new problems? In fixing a bug, developers occasionally break other pieces of code. Have related features been broken by the fix? Play around a bit, file any new bugs you find.

[edit] How to update the bug with your findings

After you've done those four steps, you probably know whether the bug is fixed or not. Here's what to do if you think it's fixed -- or what to do if you see a problem.

  • Looks Fixed? If you're convinced the bug is fixed, add a sentence or two to the bug report to explain your reasoning in verifying it. Always include your operating system (e.g. Mac OS X 10.4.5 or Windows XP SP2) and the build of Flock that you used.

Here's how bug #2553 was marked verified:

 ------- Comment #2 From Eli Goldberg 2006-02-17 17:29 -8 [reply] -------
 
 Verified fixed in:
 - Mac OS 10.3.9 (build 1140168879)
 - Windows XP SP2 (build 1140168133)
 
 The tagbox now has borders. I note that the tagbox's right edge is misaligned
 with the right edges of the other fields, and will file a separate trivial bug
 on that.
  • See a Problem? If the bug doesn't appear to be entirely fixed, add a sentence or two explaining the remaining problems.

Here's how bug #2137 was marked re-opened:

 ------- Comment #8 From Eli Goldberg 2006-02-10 14:31 -8 [reply] -------
 
 Re-opened.
 
 Although this looked OK on Mac build #1139597054 (only checked Find and Select
 All in the Favorites Manager), it does not appear fixed on Windows build
 #1139595624.
 
 Specifically, on Windows, neither Cntl+F or Cntl+A had any effect when opening
 the Favorites Manager unless I placed focus explicitly.

If you found corner cases or other side-issues, submit new bug reports, and mention their bug numbers in the bug you're verifying. Otherwise, you may "morph" critical bugs into trivial or entirely unrelated issues.

[edit] Congratulations! You've verified your first bug.

After you've verified a few bugs and have earned our trust, a Flock tester will upgrade your Bugzilla account. With this upgrade, you'll be able to change the bug's status in the Bugzilla database to "Verified" or "Re-opened". Until then, a Flock tester will see your comments in the bug and change the status for you.

If you had problems or would like to talk, visit the team in our IRC chat room, (#flock-dev on irc.flock.com), or ask on the Flock-QA email list.