QA/Test Days: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 95: Line 95:


== Past Events ==
== Past Events ==
* Apr 22, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110422 Firefox Aurora Testday]
* Apr 01, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110401 Blocker-nom Bugday]
* Mar 25, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110325 Mozmill Crowd+Endurance Testday]
* Mar 25, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110325 Mozmill Crowd+Endurance Testday]
* Mar 4, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110304 Addon Compatibility Testday]
* Mar 04, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110304 Addon Compatibility Testday]
* Feb 4, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110204 Firefox 4 Fixed Bugday]
* Feb 04, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110204 Firefox 4 Fixed Bugday]
* Jan 20, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110120 l10n Triage Testday]
* Jan 20, 2011: [https://wiki.mozilla.org/QA/Test_Days/20110120 l10n Triage Testday]

Revision as of 17:41, 5 May 2011

Testdays & Bugdays

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

Testdays Bugdays
Where irc.mozilla.org #testday irc.mozilla.org #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

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

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.

Tips

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

Join #bugday, #testday, or #qa on IRC 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 calendar for upcoming events before planning your event.

Tools
Topics
  • 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.

May 2011
Date Event
May 6, 2011 Firefox Aurora Bugday (kbrosnan)
May 13, 2011
May 20, 2011
May 27, 2011

Past Events