QA/Community/Bug Day: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
(→‎Schedule: GMT+2)
(Formatting)
 
(84 intermediate revisions by 8 users not shown)
Line 1: Line 1:
'''[[Mozilla_QA_Community|&laquo; back to Mozilla_QA_Community]]'''
== Contacts ==
= Welcome to the Mozilla QA Community Bug Day wiki!! = 
Outdated:
'''Join us on IRC in #bugday every Tuesday to discuss Bugzilla bugs and get help from the Mozilla QA team.'''
* [[IRC]] ([[Mozilla IRC Server]]): #qa


Bug 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. We gather together at predetermined times to focus on particular areas in Bugzilla. The exact area or topic for Bug Day may vary week to week. But the general idea is to work through some sort of bug list as a team.
== Welcome to the Mozilla QA Community Bug Day wiki!! == 


= Topic of the Day =
Join us on IRC any time to talk about QA at Mozilla.
* '''The Search of the Dupme/DUPEME!''' - Tue. 3/13
** Help us clean up Bugzilla by finding newer bugs that might be dups of other older bugs.
** Searching for "dupme" in the status whiteboard will often reveal a lot of bugs that people think might be dups.
** You can also use the todays Bugquerys:
***http://tinyurl.com/2h322u for Bugs with Dupme/Dupeme Status changed within 8 months
***http://tinyurl.com/yutqjf  for Bugs with Dupme/Dupeme Status last change within 12 months
***http://tinyurl.com/2ccjoj for all Bugs with Dupme/Dupeme Status (longer list)
** Before marking any bug a duplicate, please investigate both bugs thoroughly and find a second person to confirm!
** To prepare, you can check out:
*** http://www.mozilla.org/quality/help/beginning-duplicate-finding.html
***http://www.mozilla.org/quality/help/screening-duplicates.html
** ''Identifying and marking duplicate bugs helps the Mozilla community focus on the real issues by removing the noise that comes with multiple bugs about the same problems.''


== Search for Dupes of Fixed Bug in Firefox 2.0.0.3/1.5.0.11 - Verify Fixed Bugs ==
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.
* Firefox 2.0.0.3 and 1.5.0.11 is coming soon and some Bugs are fixed in this release
* Fixed Bugs
** https://bugzilla.mozilla.org/show_bug.cgi?id=371576 - Backbase bug
** https://bugzilla.mozilla.org/show_bug.cgi?id=373181 - Subscribing to RSS feeds
** https://bugzilla.mozilla.org/show_bug.cgi?id=371925 - Rendering problems for tfoot
** https://bugzilla.mozilla.org/show_bug.cgi?id=370136 - Firefox 2.0.0.1 and later breaks automatic client certificate authentification
** https://bugzilla.mozilla.org/show_bug.cgi?id=371525 - Password Trouble with Multiple Accounts
* You can play test this bugs (as example Bug 371525 Password Trouble with Multiple Accounts) just do some test with the steps to reproduce in this bugs and see if you can verify this bug as fixed.
* Then you could do some searches for dupes of this bugreports


= Getting Started =
== Next Bug Day==


While the topic of day may have a particular focus for the session, we always want to try to do the following:
=== TBD ===


* Replicate the problems specified in bug reports and mark them as "confirmed" whenever we are able to do so.
As of April 2014:
* Clarify bug reports whenever we can do so without distorting the problems.
* Close bug reports as WORKSFORME or INVALID when it's appropriate to do so.
* Ask reporters to provide missing information that would help to replicate and ultimately fix the bugs they report.


''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.''
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays.
[[Bugdays/Bug-verification | Bug Verification]] days are on Wednesday!


= Schedule =
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!
Bug days are arranged into three sessions so as to be convenient for participants around the world. The three sessions target "prime time" for those in Asia/Australia, Europe/Africa, and North/South America, but anyone may attend the sessions as they wish.


The table below shows the three sessions, as well as how the times for each of the sessions translate into various time zones.
= Future Bug Days =
Please find future topics on the [https://quality.mozilla.org/category/events/ QMO events calendar]


{| border="1"
= Staying Connected =
|-
Join the mailing list - <s><code>https://lists.mozilla.org/listinfo/dev-quality</code></s>
! Timezone \ Session
<br>Hang out in [[#Contact | IRC]] when we're not scheduled in #testday
! East Asia / Australia
<br>Watch the [https://quality.mozilla.org/category/events/ QMO Events page] for new event announcements.
! Europe / Africa
! Americas
|-
! GMT-10 Hawaii
| Tue 01:00-03:00
| Tue 09:00-11:00
| Tue 16:00-18:00
|-
! GMT-7 N.America, PST*
| Tue 04:00-06:00
| Tue 12:00-14:00
| Tue 19:00-21:00
|-
! GMT-6 N.America, MDT*
| Tue 05:00-07:00
| Tue 13:00-15:00
| Tue 20:00-22:00
|-
! GMT-5 N.America, CDT*
| Tue 06:00-08:00
| Tue 14:00-16:00
| Tue 21:00-23:00
|-
! GMT-4 N.America, EST*
| Tue 07:00-09:00
| Tue 15:00-17:00
| Tue 22:00-00:00
|-
! GMT UK/Ireland
| Tue 11:00-13:00
| style="border-right: 1px solid black;" | Tue 19:00-21:00
| style="border-top: 2px solid black" | Wed 02:00-04:00
|-
! GMT+1 Europe, CET
| Tue 12:00-14:00
| style="border-right: 1px solid black" | Tue 20:00-22:00
| Wed 03:00-05:00
|-
! GMT+2 Europe
| Tue 13:00-15:00
| style="border-right: 1px solid black" | Tue 21:00-23:00
| Wed 04:00-06:00
|-
! GMT+3 Moscow
| Tue 14:00-16:00
| style="border-right: 1px solid black" | Tue 22:00-00:00
| Wed 05:00-07:00
|-
! GMT+8 Beijing
| style="border-right: 1px solid black;" | Tue 19:00-21:00
| style="border-top: 2px solid black" | Wed 03:00-05:00
| Wed 10:00-12:00
|-
! GMT+9 Japan
| style="border-right: 1px solid black;" | Tue 20:00-22:00
| Wed 04:00-06:00
| Wed 11:00-13:00
|}


Some of us hang around between or after sessions, so you may find someone in #bugday outside of this time, and if not, you can always find people in #qa.
= FAQ =


* Calculated with DST
'''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:


= Community Representatives =
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.


Bug days are led by Mozilla's QA staff and by experienced volunteers from our community.
''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.''


= Staying Connected =
'''What to do next?'''
* Click [http://mail.mozilla.org/listinfo/communityqateam here] to join the mailing list.
* Hang out in #qa when we're not scheduled in #bugday or #testday
* Keep an eye on this page. Weekly updates will be posted by Thursday afternoon (California time)
* Read the [http://weblogs.mozillazine.org/qa/ Mozilla QA blog]


= FAQ =
'''Where do I start?'''
* The following documentation is good to become familiar with for anyone working on Mozilla projects:
** [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
** 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.
* Review the documentation specific to the topic of the day.
* Review the documentation specific to the topic of the day.
* Join the '''#bugday''' channel
* Join the '''#bugday''' channel
Line 137: Line 47:
*** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]  
*** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients]  
** Connect to [irc://irc.mozilla.org irc.mozilla.org] and "/join #bugday"
** 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 [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ the latest Firefox Trunk builds], the next version of Firefox in development.


'''Bug Day History'''
== Community Representatives ==
* [http://www.mozillazine.org/talkback.html?article=954 Asa's "Original" Bug Day post]
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]]
* [http://weblogs.mozillazine.org/qa/archives/2006/04/bug_day_revival_starts_may_2_2.html Tracy's "Bug Day Revival" QA Blog post]

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"