Difference between revisions of "Thunderbird TestDay"
(→Time and Location) |
|||
| Line 3: | Line 3: | ||
== Time and Location == | == Time and Location == | ||
| − | Friday, Dec 1, 2006 at 11:40 EST at Rm. | + | Friday, Dec 1, 2006 at 11:40 EST at Rm???. |
Duration : 2 hours | Duration : 2 hours | ||
| − | |||
== Preparation == | == Preparation == | ||
Revision as of 00:12, 24 November 2006
Time and Location
Friday, Dec 1, 2006 at 11:40 EST at Rm???.
Duration : 2 hours
Preparation
Everyone who want to contribute to this project must sign up for an Bugzilla account and email your user id to Eva at yeor@learn.senecac.on.ca 2 days priors to the event.
This event host as a competition, the calendar QA team will announce a winner who contributes the most to this event. Prize will be given to the winner.
Hence, how can you prepare yourself for this event? First of all, you will need to get familar with Bugzilla. We will not be using litmus in this event. This link is a documentation on what to do an what not to do in bugzilla.
Calendar QA goal is to clean out the bugzilla backlog so new functionality can be test soon. Therefore, they need to:
- Confirm unconfirmed bugs - ensure that the bugs are reproducible and not duplicates of known issues. A documented guide is provide in this link.
- Verify existing fixed - ensure that the fixes did fix the problem in the bug report and did not cause other regressions. In this case, you need to how the find the bugs that is fixed and how to change its status after you verified it.
- Investigate on defects that are flagged as QAWanted. provide more details, analysis, and clearer or simpler steps to reproduce the issue.
Here is a previous Calendar Test Day example
