The Gecko BugAThon 300 Starts!
Monday June 28th, 1999
Help Mozilla and win prizes! Many bugs in the bugzilla database are suffering from blank status lines, and need to be resolved to the simplest possible test case. When the coders have to do this themselves, it prevents them from using their time to fix the bug. So, mozilla.org is giving away prizes to people who clean up these bugs by providing "simplest test cases".
The complete rules for the contest can be found by clicking "Full Article" below. Prizes given away by mozilla.org include invitations to the Gecko launch party, Gecko stuffed animals, and autographed Gecko T-Shirts.
So, get cracking, and clean up those bugs!
#1 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 10:32 AM
Typical ;-> finnaly an assignment i could qualify for, and then I'm not home to do it.
but it is a damm good idea
#2 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 11:20 AM
What about all the bugs I've already analyzed/reproduced/made testcases for? What about the bugs I reported that were then fixed (that weren't dupes)? I know some serious bug reporters could get the t-shirt just by changing a bunch of the bugs they were working on....
#3 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 12:12 PM
I know. I already sent in five bug reports that led to fixes in some form or another. Where's my invite? ;)
#4 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 12:36 PM
I would really like to help, can someone tell me if I need to be a programmer to fix these bugs?
#5 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 12:47 PM
You're not fixing bugs, just fixing bug reports - making sure that there's a simple test case for each of them, so the bug-fixer doesn't have to wade through a lot of crap to figure out what the exact problem is.
#6 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 2:44 PM
Come on, lets all chip in, prizes or no prizes :-)))
there are near 800 bugs on the M8 list. (total bug count = 2200) AFAIR
#7 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 4:22 PM
Having spent a bit of time looking through kipp's and karnaze's bugs in the past, I think karnaze's bugs are probably most in need of this work (I haven't looked at the bugs of the other two much, though). More of kipp's bugs are already simplifed than karnaze's, I think. Simplifing many of karnaze's bugs is hard work, because many of them are "Page X is messed up" where Page X uses incredibly complicated tables-for-layout. But it's also very important work - somebody needs to do it (more than one person, too). Simplifying these bugs is not as easy as most others.
BTW, does five bugs qualify one as a "serious bug reporter"? I've submitted 243 so far. :-)
#8 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 4:39 PM
David, you should get a medal. Even though I'm not a Mozilla coder, I really appreciate all the work you've done. Your work has been a great benefit to the Mozilla effort.
#9 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 4:58 PM
"BTW, does five bugs qualify one as a "serious bug reporter"? I've submitted 243 so far. :-)"
Heh, great work. You should get AOL to send you 12 t-shirts, each autographed by every raptor engineer. After all, it's not like they have anything better to do ;)
#10 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 5:18 PM
I'm still confused as to what to do. What is a "simplest test case?" What are we supposed to do, go through the code and see what is screwing up?
#11 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 5:27 PM
"What are we supposed to do, go through the code and see what is screwing up?"
Exactly. Create a sample page with only the code that causes the problem. Or, determine that the sample code that's presented is simplified enough already. If you're right, you'll get points either way.
#12 Re:The Gecko BugAThon 300 Starts!
Monday June 28th, 1999 5:35 PM
Go through karnaze's bugs using the link in the full article. There have been some busy people already putting testcases out there. Look at a few good examples. Basically you need to write a page and explain what it should look like when the problem is fixed.
Be sure to put [TESTCASE] in the status whiteboard field when you add your test to bugzilla. Some bugs had the comment added to the description rather than the status whiteboard so it is harder to figure out if a test has already been written.
#13 Almost July 26th
Thursday July 22nd, 1999 4:23 PM
Hey there folks. Just a wakeup reminder that the Bugathon is supposed to end in 4 days.
Some of the listed developers have many new bugs that also need testcased.