QA/Test Days: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
Line 97: Line 97:
  |-
  |-
  | July 29, 2011
  | July 29, 2011
  |
  | Sync in aurora (focus around discovery and instant sync)
  |}
  |}


Revision as of 15:51, 20 July 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 schedule for upcoming events before planning your event.

Tools
  • Checklist - use this to track planning, execution, and wrap up of your event
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
Suggestions

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.

July 2011
Date Event
July 1, 2011 Mozmill (whimboo)
July 8, 2011 SUMO Users&Groups/ Private Messaging (rbillings)
July 15, 2011 Firefox 6 Beta desktop & mobile (marcia, aaronmt)
July 22, 2011
July 29, 2011 Sync in aurora (focus around discovery and instant sync)
August 2011
Date Event
August 5, 2011 Firefox 7 Aurora (ashughes)
August 12, 2011
August 19, 2011 AMO Automation (mcompton)
August 26, 2011 Firefox 7 Beta (ashughes)
September 2011
Date Event
September 2, 2011
September 9, 2011
September 16, 2011 Firefox 8 Aurora (juanb)
September 23, 2011
September 30, 2011

Past Events

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Test_Days&oldid=331444"