QA/Community/Bug Day: Difference between revisions

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


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.
== Welcome to the Mozilla QA Community Bug Day wiki!! ==  


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


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.
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.


Hope to see you in #qa.
== Next Bug Day==


-tracy
=== TBD ===


= Topic of the Day: Tabbed Browsing =
As of April 2014:


'''Tuesday, July 11, 2006'''
[[Bugdays/Bug-Triage | Bug Triage]] days are generally Fridays.
*Firefox 2.0 Tabbed Browsing:  Confirm, verify and file new bugs for the improved tabbed browsing features in Firefox 2.0beta1 builds
[[Bugdays/Bug-verification | Bug Verification]] days are on Wednesday!
**Bugs to verify: [http://tinyurl.com/fyyfp resolved bugs]
**Check the [http://tinyurl.com/jtbuw open bugs] list before filing new ones.


*next week: Top site testing and report a broken/phishing website.
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!


= Review of last week =
= Future Bug Days =
'twas a national Holiday in USA, no particpants in Bug Day.
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 documentation 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://irc.mozilla.org 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 =
 
'''Tuesday, July 11, 2006'''
*Firefox 2.0 Tabbed Browsing:  Confirm, verify and file new bugs for the improved tabbed browsing features in Firefox 2.0beta1 builds
**Bugs to verify: [http://tinyurl.com/fyyfp resolved bugs]
**Check the [http://tinyurl.com/jtbuw open bugs] list before filing new ones.
 
*Again no participants in bug day. However, I verified 20 bugs in tabbed browser.
 
'''Week 10: Tuesday, July 4, 2006'''
*Back to Basics:  General help for new bugzilla users
** [https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html Bug Writing Guidelines]
* no participants due to holiday
 
'''Week 9: Tuesday, June 27, 2006'''
* Bug Day off; host at MoFo quarterly meetings
 
'''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 : [http://tinyurl.com/e6haf fixed1.8.0.5 bugs]
*** Verified 20 1.5.0.5 Firefox bugs
 
'''Week 7: Tuesday, June 13, 2006'''
*Finding Dupes:  How to find duplicate reports.
**Please read Sean Richardsons's [http://www.mozilla.org/quality/help/screening-duplicates.html Screening Duplicate Bugs], it is an excellent primer for duplicate bug finding.
**We'll be working this [https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIRMED&changedin=2&product=Core&product=Firefox&product=Thunderbird Bug List] of recently filed unconfirmed Firefox bugs.
**I'll explain Asa's clever use of [https://bugzilla.mozilla.org/query.cgi?format=specific 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
** [https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html 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'''
*'''[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"