QA/Community/Bug Day: Difference between revisions
| Line 8: | Line 8: | ||
'''Week 2: May 9, 2006''' | '''Week 2: May 9, 2006''' | ||
*'''[http:// | *'''[http://www.mozilla.org/newlayout/bugathon.html 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: | ||
** [https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&component=Layout&keywords=testcase&keywords_type=nowords&cmdtype=doit Unconfirmed Gecko Layout bugs] | |||
** | |||
= Review of last week = | = Review of last week = | ||
Revision as of 14:11, 15 May 2006
Welcome to the Mozilla QA Community Bug Day wiki!!
When Asa changed his focus to marketing and spreadfirefox, a huge void in QA was left behind. Mozilla QA would like to try to fill some of that void by reviving weekly community Bug Days. 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'll be scheduling a guest Dev or QA member to join us each week as well.
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.
Topic of the Day
Week 2: May 9, 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:
Review of last week
Very few interested participants last week :-( The topic was complex. Basically any topcrash bugs that got attached to the reports was my doing. Jay and I walked through an example to help demystify the talkback topcrash analysis process. But no one showed enough interest or had time to focus on our demo. Oh well, moving on.
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 Firefox builds here
Past Bug Day Archives
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.