QA/Community/Bug Day: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
(Formatting)
 
(233 intermediate revisions by 11 users not shown)
Line 1: Line 1:
= Welcome to the Mozilla QA Community Bug Day wiki!! =
== Contacts ==
Outdated:
* [[IRC]] ([[Mozilla IRC Server]]): #qa


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.
== 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.
Join us on IRC any time to talk about QA at Mozilla.


= Topic of the Day =
Test Days are 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 exact area or topic for Bug Day will vary for each event. But the general idea is to work through some sort of bug list as a team.


'''Week 5: Tuesday, May 30, 2006'''
== Next Bug Day==
*Open week:  tracy is unprepared for any specific topic
** tracy will be hanging out in #qa to take any other ideas or suggestions for bug days and answer any bug day related questions.  I may bot be there the entire 4 hour block.  If the channel goes quiet bug wise, I'm gonna do some office/system rearranging.
*next week we'll be doing a back to basics Bug Day.  In fact I think it might be a good idea to hold a back to basics day the first Tuesday of each month.


= Review of last week =
=== TBD ===
Very few interested participants again last week :-(  Time to rethink our strategy.
 
As of April 2014:
 
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays.
[[Bugdays/Bug-verification | Bug Verification]] days are on Wednesday!
 
Join us in #testday and introduce yourself. In triaging, we go through newly reported bugs. For verification, we try to make sure that "fixed" bugs really are fixed. See you in #testday!
 
= Future Bug Days =
Please find future topics on the [https://quality.mozilla.org/category/events/ QMO events calendar]
 
= Staying Connected =
Join the mailing list - <s><code>https://lists.mozilla.org/listinfo/dev-quality</code></s>
<br>Hang out in [[#Contact | IRC]] when we're not scheduled in #testday
<br>Watch the [https://quality.mozilla.org/category/events/ QMO Events page] for new event announcements.


= FAQ =
= FAQ =


'''Where do I start?'''
'''Where do I start?'''
* The following documantation is good to become familiar with for anyone working on Mozilla projects:
Each Bug Day topic will have a specific focus. Instruction on what needs to be done should be included in the QMO Bug Day Event post:
** [http://www.mozilla.org/quality/ Mozilla QA] linked to from the "For Testers" section of [http://www.mozilla.org/developer/ mozilla.org/developer]
 
** A [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html good document] on how to find existing bugs
The following documentation is good to become familiar with for anyone trying to work in Bugzilla projects:
** Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn how to write effective bug reports that lead to bug fixes.
* Read [http://www.mozilla.org/quality/bug-writing-guidelines.html Bug Writing Guidelines] to learn how to write effective bug reports that lead to bug fixes.
 
''Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.''
 
'''What to do next?'''
 
* Review the documentation specific to the topic of the day.
* Review the documentation specific to the topic of the day.
* Join the #qa channel
* Join the '''#bugday''' channel
** Go to your favorite IRC client  
** Go to your favorite IRC client  
*** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]
*** [http://www.ircreviews.org/clients/platforms-windows.html Windows clients]
*** [http://www.ircreviews.org/clients/platforms-macos.html MacOS clients]
*** [http://www.ircreviews.org/clients/platforms-macos.html MacOS clients]
*** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]  
*** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]  
** Connect to irc.mozilla.org and "/join #qa"
** Connect to [irc://irc.mozilla.org irc.mozilla.org] and "/join #bugday"
** Then, just ask the moderators how you can help for the topic of the day.
** Then, just ask the moderators how you can help for the topic of the day.
 
'''What build should I be testing with?'''
*Get [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8 the latest Bon Echo builds], the release of the Firefox browser still in development.
 
= Past Bug Day Archives =
 
'''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'''
*'''[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]
 
 
 
'''Week 2: May 9, 2006'''
*'''[http://wiki.mozilla.org/Talkback_Topcrash_Analysis 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'''
== Community Representatives ==
*'''[[Mozilla_QA_Community:Talkback:Reproduce_Crash_Bugs | Reproducing Crash Bugs]]''' - learn more about what we'll be doing during our Bug Day!
Bug days are led by members of Mozilla's QA staff. We are always willing to guide and teach communities members who are willing to take on more responsibility. If you want to host or moderate a Bug Day, Please let us know. For contributors planning and hosting Bug Days please see the [[QA/Community/Bug Day/Planner|Bug Day Planner]]
*Scheduled guest: Jay Patel - Talkback Guru and 1.5.0.4 QA lead.

Latest revision as of 23:11, 31 January 2024

Contacts

Outdated:

Welcome to the Mozilla QA Community Bug Day wiki!!

Join us on IRC any time to talk about QA at Mozilla.

Test Days are 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 exact area or topic for Bug Day will vary for each event. But the general idea is to work through some sort of bug list as a team.

Next Bug Day

TBD

As of April 2014:

Bug Triage days are generally Fridays. Bug Verification days are on Wednesday!

Join us in #testday and introduce yourself. In triaging, we go through newly reported bugs. For verification, we try to make sure that "fixed" bugs really are fixed. See you in #testday!

Future Bug Days

Please find future topics on the QMO events calendar

Staying Connected

Join the mailing list - https://lists.mozilla.org/listinfo/dev-quality
Hang out in IRC when we're not scheduled in #testday
Watch the QMO Events page for new event announcements.

FAQ

Where do I start? Each Bug Day topic will have a specific focus. Instruction on what needs to be done should be included in the QMO Bug Day Event post:

The following documentation is good to become familiar with for anyone trying to work in Bugzilla projects:

Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.

What to do next?

Community Representatives

Bug days are led by members of Mozilla's QA staff. We are always willing to guide and teach communities members who are willing to take on more responsibility. If you want to host or moderate a Bug Day, Please let us know. For contributors planning and hosting Bug Days please see the Bug Day Planner

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Community/Bug_Day&oldid=1249867"