QA/Test Days OLD

From MozillaWiki
< QA
Jump to: navigation, search

This article is deprecated, see our QMO documentation. Text below is for historical goal.

Testdays & Bugdays

We have two main types of test events. The following is a summary of their differences.

Testdays Bugdays
Where #testday #bugday
When Any day of the week (mostly Friday) Any day of the week (mostly Friday)
What Helping to test and find bugs Triaging existing bug reports

Testdays are more about product testing. Most testdays involve testing a particular feature or product. Usually these features are brand new and need people to test them before they go out to a wider public audience. Testdays usually follow a predefined test plan written by the testday organizer.

Testdays are the easiest entry point for people wanting to learn about testing.


Bugdays are more about bug testing. Most bugdays involve going through bug reports from a predefined set of bugs. The activities can be more technical in nature, depending on the specific bug reports. The simplest of activities is testing the claim of the bug and trying to reproduce it. The more complex activities involve attempting to reproduce regression ranges and crashes.

Bugdays are the easiest entry point for people wanting to learn about Firefox bugs.


I don't know the first thing about testing and bugs.

Join #bugday, #testday, or #qa on Mozilla IRC Server and ask us for help. We are more than happy to teach you everything you need to know!

Want to know how to write a bug?

Check out the bug writing guidelines.

I don't have access to make changes to bugs.

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 on IRC in the #bugday, #testday, or #qa channel; one of the moderators or an experienced volunteer will assist you.

Staying Connected

Want to stay connected to testing between test events? Here are some tips for how you can stay connected to Mozilla QA and testing between the testdays and bugdays.

Organizing a Test Event

Check the schedule for upcoming events before planning your event.

  • Checklist - use this to track planning, execution, and wrap up of your event
  • Testdays
    • new Firefox feature
    • new Firefox release
    • old Firefox feature with recent changes
    • teaching people about different types of testing
  • Bugdays
    • confirming unconfirmed bugs
    • verifying fixed bugs
    • verifying duplicate bugs
    • finding regression ranges
    • finding steps to reproduce specific bugs
    • finding reliable crash scenarios
    • writing tests for specific bugs
    • check the bugday archive for other ideas

Upcoming Schedule

"Firefox Fridays!": Aim to have a "testing" event every Friday

Check the calendar for upcoming events. If one is not already booked, please add the date, your name, and the event you are planning. You should do this well in advance to ensure your date is available.

September 2011
  • 2011-09-02: QA-WANTED UNCO (ashughes)
  • 2011-09-09: Socorro (mbrandt) CANCELED
  • 2011-09-16: SUMO Reports (softvision)
  • 2011-09-23:
  • 2011-09-30: BrowserID (jbonacci) + Dev Demo (Dan Mills)
October 2011
  • 2011-10-07:
  • 2011-10-14:
  • 2011-10-21:
  • 2011-10-28:

Past Events