QA/Community/Bug Day
Welcome to the Mozilla QA Community Bug Day wiki!!
For those of you unfamiliar with Bug Days; a topic or area of focus is selected by the host. Then with all your help, we'll attempt to complete as much of the task as possible. Bug Days is an excellent way to contribute to Mozilla's QA efforts. It doesn't matter if you've been involved with Mozilla for years or if this is your first step into our amazing open source community. Anyone can participate and be a valuable contributor. The real purpose of Bug Days is to generate interest from the community to contribute to Mozilla projects.
I'll be in #qa every Tuesday from 12:00pm to 4:00pm Pacific Daylight Time to coordinate and guide your efforts in the bug topic of the week. (I am considering moving this up a few hours in order to make it more convenient for our friends in Europe to participate.)
We need to generate more interest in Bug Days from contributors new to Mozilla and Bugzilla. So first Tuesday of each month will be "Back to Basics" Bug Day. I'll be there to help anyone out with writing their first bug, querying Bugzilla and general Bugzilla Q & A. Veterans don't despair, please come on first Tuesdays to help the new folk. Also, if there is interest in working on something more specific, bring it up and we can get on it as well. Conversely, on Tuesdays the rest of the month, new users should feel welcome to come in and ask for basic help, even if it's unrelated to the topic of the day.
Hope to see you in #qa.
-tracy
Topic of the Day: Verifying Bugs
Week 8: Tuesday, June 20, 2006
- Verifying Bugs: Complete the bug life cycle; verify the bug is actually fixed!
- We'll be working a short list of Firefox 1.5.0.5 FIXED bugs : fixed1.8.0.5 bugs
- Debate on bug verification.
- Thousands of bug fixes go unverified every month. Does it matter?
- It does seem like a ton of make work because a very high percentage of bugs that are marked fixed are correctly and truly fixed. Occasionally though, fixes go in that leave the bug broken or cause other breakage. Is the effort needed to plow throw long lists of verified bugs worth the return of discovering a small percentage of unfixed/regressed bugs?
- What methods can we use to better handle this final step in a bugs life.
- Community QA module owners?
- Each developer recruit a QA partner(s)?
- Forget it?
- Suggestions...
- next week: Bug Day will be taking the day off: Host at Quarterly Mozilla Onsite meetings. I'll back on Tuesday, July 4th at our regular time. (yeah, it's a US national holiday, but a lot of our Bug Dayers have been from outside the US. To keep things going, I'll be here). Since that's first Tuesday of the month, we'll be doing Back to Basics.
Review of last week
Only a few participants in bug day again. But they were all three fairly new to bugzilla and were eager to learn. That's encouraging. I hope to see them back in the coming weeks and hope to see more new folk join Bug days as time goes by. A few Vet's in #qa chimed in here and there with their tips and tricks. Thanks for a good Bug Day!
FAQ
Where do I start?
- The following documantation is good to become familiar with for anyone working on Mozilla projects:
- Mozilla QA linked to from the "For Testers" section of mozilla.org/developer
- A good document on how to find existing bugs
- Read Bug Writing Guidelines to learn how to write effective bug reports that lead to bug fixes.
- Review the documentation specific to the topic of the day.
- Join the #qa channel
- Go to your favorite IRC client
- Connect to irc.mozilla.org and "/join #qa"
- Then, just ask the moderators how you can help for the topic of the day.
What build should I be testing with?
- Get the latest Bon Echo builds, the release of the Firefox browser still in development.
Past Bug Day Archives
Week 7: Tuesday, June 13, 2006
- Finding Dupes: How to find duplicate reports.
- Please read Sean Richardsons's Screening Duplicate Bugs, it is an excellent primer for duplicate bug finding.
- We'll be working this Bug List of recently filed unconfirmed Firefox bugs.
- I'll explain Asa's clever use of Find A Specific Bug to uncover dupes.
- Two new users came and learned how to dupe bugs. One other we gave can confirm privs for his work in Tbird bugs.
Week 6: Tuesday, June 6, 2006
- Back to Basics: General help for new bugzilla users
- Bug Writing Guidelines
- Walked through how to triage unconfirmed with three users fairly new to Bugzilla.
Week 5: Tuesday, May 30, 2006
- Open week: no topic prepared
- Tracy hung out in #qa for an hour. No visitors interested in Bug Day
Week 3-4: Tuesday, May 16 and May 23 , 2006
- Gecko Layout Bugathon - We'll be pulling double duty of sorts this time around; As some triage and testcase reduction for unconfirmed layout bugs will be on our plate. We'll be working from the list below:
Week 2: May 9, 2006
- Talkback Topcrash Analysis - We'll be finding, creating and/or adjusting crash bugs so they appear on the Talkback Topcrash Reports. We will focus on the current Bon Echo (Firefox 2) branch.
- Current Talkback Reports for the Bon Echo (Firefox 2) branch:
- for current topcrashers on the Firefox 2 branch, you can go here: http://talkback-public.mozilla.org/reports/firefox/FF2x/index.html
- for old topcrashers at the time of alpha 1 (3/21), check out http://talkback-public.mozilla.org/reports/firefox/FF2a1/index.html
- Scheduled guest: Jay Patel - Talkback Guru and 1.5.0.4 QA lead.
Opening Day: May 2, 2006
- Reproducing Crash Bugs - learn more about what we'll be doing during our Bug Day!
- Scheduled guest: Jay Patel - Talkback Guru and 1.5.0.4 QA lead.