Thunderbird:QA TestDay:2010-03-25

From MozillaWiki
Jump to: navigation, search

last testday | index | next testday »

Bug Day March 25, 2010

How to get help, how to get started, and schedule for Bugdays.

Bug days are conducted to reduce the number of UNCOnfirmed bugs in the bugzilla database, and to improve the quality of the bugs in the database.


Help shape Thunderbird 3.1. And help trunk testers who help us by reporting bugs.

Below is a list of bugs That were reported when people migrated from Thunderbird 2.x to 3.x. The goal of the bugday is to :

  1. Determine if the UNCO bugs are movable to NEW
  2. Mark duplicates bug that can be
  3. try to gather more information


You can ask help during the event here (this link will make you join #tb-qa on irc where most of us are available to provide help).

Before starting, see the Bugdays page for information about what to do and how to get help. Don't be concerned if you don't understand everything, just ask for help.

Searching in bugzilla can be tricky - here are a few tricks that might help.


For this bugday, the times of the sessions, accounting for 30mins [1] of grace period before and after each session, were as follows:

  • Session 1
    • Start time: 2010-03-25 0530h PDT
    • End time: 2010-03-25 0830h PDT
  • Session 2
    • Start time: 2010-03-25 1130h PDT
    • End time: 2010-03-25 1430h PDT
  • Session 3
    • Start time: 2010-03-25 1830h PDT
    • End time: 2010-03-25 2230h PDT
  • 17 hour duration
    • All sessions & intermediate rest time.
    • Start time: 2010-03-25 0530h PDT
    • End time: 2010-03-25 2230h PDT
Bug Day results
Sessions Product Any Change Only Resolution Change [2]
Session 1 Thunderbird-only Q 20 Q 27 Q 11 Q 15
Core-only Q 7 Q 4
Session 2 Thunderbird-only Q 23 Q 28 Q 6 Q 7
Core-only Q 5 Q 1
Session 3 Thunderbird-only Q 12 Q 18 Q 2 Q 3
Core-only Q 6 Q 1
17 hour Duration Thunderbird-only Q 88 Q 122 Q 23 Q 33
Core-only Q 34 Q 10

Many thanks to volunteers and developers (total 0 - 5) who turned up for this bug day, and others that I may have possibly missed.


  • Spreadsheet of bugday results is compiled and updated after each session / bugday.
  • The letter Q stands for the query with all the appropriate criteria, which over time may differ from the results that have been logged.
  • [1] Session and period time includes 30mins before and after the official time period, so as to include early and late/spill over activity.
  • [2] A resolution change may be non-terminal, for example a bug may have been reopened.