Thunderbird:QA TestDay:2009-08-06
last testday | index | next testday »
Bug Day August 6th, 2009
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.
Focus
Help shape Thunderbird 3. And help trunk testers who help us by reporting bugs.
This week's focus is going to be try to clean up duplicates. Duplicates are bugs that have been reported more than once in bugzilla. Sometimes it's reported twice because people don't search they report directly, sometimes it's just very difficult to find the duplicate. Having one bug per issue reduces the time it takes for this issue to get solved, this is why we want to find bugs that are duplicates. Bug that might be duplicates are marked with a special keyword - because someone reading the bug thought It already had seen the issue.
- The goal this week is to find duplicates and mark them as such.
- It's also interesting to know if the bugs are not duplicates - if they are not think about removing the keyword, and if they are in the UNCO state.
- Adding a comment about the bug being reproducible is valuable too.
- If you don't have the rights to resolve bugs - cc ludovic@mozillamessaging and I will do it for you.
Lists of bugs :
- Thunderbird bugs flagged as possible duplicates (89)
- bugs affecting Seamonkey and Thunderbird flagged as possible duplicates (37)
Duplicate the less active bug to the more active one !
Tips
You can ask help during the event here or on chat.mozillamessaging.com. And if you don't get an answer immediately please be patient.
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.
Results
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: 2009-08-06 0530h PDT
- End time: 2009-08-06 0830h PDT
- Session 2
- Start time: 2009-08-06 1130h PDT
- End time: 2009-08-06 1430h PDT
- Session 3
- Start time: 2009-08-06 1830h PDT
- End time: 2009-08-06 2230h PDT
- 17 hour duration
- All sessions & intermediate rest time.
- Start time: 2009-08-06 0530h PDT
- End time: 2009-08-06 2230h PDT
Sessions | Product | Any Change | Only Resolution Change [2] | ||
---|---|---|---|---|---|
Session 1 | Thunderbird-only | Q 6 | Q 10 | Q 0 | Q 0 |
Core-only | Q 4 | Q 0 | |||
Session 2 | Thunderbird-only | Q 7 | Q 11 | Q 1 | Q 1 |
Core-only | Q 4 | Q 0 | |||
Session 3 | Thunderbird-only | Q 11 | Q 18 | Q 2 | Q 2 |
Core-only | Q 7 | Q 0 | |||
17 hour Duration | Thunderbird-only | Q 45 | Q 68 | Q 7 | Q 8 |
Core-only | Q 23 | Q 1 |
Many thanks to volunteers and developers (total 0 - 5) who turned up for this bug day, and others that I may have possibly missed.
Notes:
- 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.