The Crash Reporter is one of the many vital tools that go into debugging issues with Mozilla products. In this session we will give a general overview of the Mozilla Crash Reporting system as well as introduce you to ways that the team analyzes the crash data. Perhaps after this discussion you will be interested in lending a hand to this exciting effort!

https://developer.moz... has more detailed information about the Crash Reporter should you interested in reading more about it prior to the meetup.

We have wireless guest access so you are welcome to bring your laptops.

We will gather at 6:30 PM for the usual pizza and soft drinks, and we will start the presentation promptly at 7 PM.

Please feel free to marcia@mozilla.org me if you have any questions.

How do I get ready?

https://developer.mozilla.org/en/Crash_reporting has more detailed information about the Crash Reporter and links to development information.

This is what we're doing...

Location:
Mozilla Headquarters
650 Castro Street, Suite 300
Mountain View, CA 94041

Start time: 6:30 PM PST. We will have pizza and mingle and the talk will start promptly at 7 PM

The MozQA community is holding a Testday on Friday, August 7th, for users interested in the use, development and/or testing of Mozmill! We're going to have the Mozmill team available to help create automated test cases, perform exploratory testing on Mozmill and just generally chat about the project for the community via IRC Chat (channel #testday on irc://irc.mozilla.org). So, if you're interested, come on by anytime between 7AM to 5PM PDT this Friday!

How do I get ready?

3. Use the MozMill Test Writing Guide and read through our test creation guide to get started.

This is what we're doing...

Join the MozQA Community in Testscripting with MozMill 1.2!
==============================================================
 
Use Pastebin URLs to send code snippets to other members. To add any testscripts created, please attach them to a bugzilla bug that will be linked in the chat room topic as well as here on the day of the testday. Make sure to follow the instructions listed.

The MozQA community is holding a Testday on Friday, July 24th, for users interested in the use, development and/or testing of the Addons group's webportal, AMO, version 5.0.8. We're going to have the awesome WebDev QA team available to help users run defined test cases, perform exploratory testing on the project's site and just generally chat about it with the community via IRC Chat (channel #testday on irc://irc.mozilla.org). So, if you're interested, come on by anytime between 7AM to 5PM PDT that Friday!

This is what we're doing...

Join the MozQA Community in testing AMO 5.0.8!
==============================================================
Currently, the testsuite is currently being set up at this time, so exploratory testing for the website is the plan, so far, for the testday. Once the testsuite has been created and ported to an online directory, its link will be posted to this event. If you've never been to AMO (Addons @ Mozilla), the website can be found here.
 
Otherwise, have fun with the event!
==============================================================

This Bug Day, we'll be focusing on unconfirmed bugs reported using Firefox 3.5. It's important to find any severe bugs that were missed during the release cycle. Any blocker, critical, or major bugs that are found could get fixed in the upcoming Firefox 3.5.1 or another maintenance release.

How do I get ready?

Meet us on #bugday for help and guidance. You can use this URL for a good search query to get started with.

This is what we're doing...

During this Bug Day, we will focus on narrowing down unconfirmed bugs to find any important ones that have been reported, looking especially for regressions in Firefox 3.5 that weren't in Firefox 3.0. Once we find them, we'll hand them off to developers to get them into a "point" update (e.g., Firefox 3.5.1).