Calendar TestDay
From Open Source@Seneca
Contents |
Result
- 16 bugs confirmed, 6 new bugs (9 new, but 3 are duplicates) in 45 mins
- JBMossop is the winner with 6 confirmation
Time and Location
Friday, Dec 1, 2006 at 11:40 EST at Rm T3073.
Duration : 2 hours
Preparation
Everyone who wants to contribute to this project must sign up for a Bugzilla account and email your user id to Eva at yeor@learn.senecac.on.ca 2 days priors to the event. This is for the Calendar QA's to assign you the Canconfirm privilege. 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. How can you prepare yourself for this event? First of all, you will need to get familiar with Bugzilla. We will not be using litmus in this event. This link contains documentation on what to do and 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
What build should I test?
We will be testing the latest nightly builds of Sunbird and Lightning:
Sunbird:
Lightning (for Thunderbird 1.5.x and 2.0 candidates):
- Note: to find the Lightning.xpi, browse to your Operating System subfolder from this directory.
:http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8/
- Please use this instead: http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/2006-11-30-03-mozilla1.8/
- Note that you only need to download the lightning.xpi from this ^^^ link. The thunderbird version from the previous link is OK.
Testing Instructions
- Download Sunbird or Lightning from the above URLs
- Create your testing profile (see above)
- To Confirm Unconfirmed Bugs:
- Click on a Bugzilla query below for a component that you would like to work on.
- Pick a bug that sounds interesting, be sure to confirm normal (nor) bugs before enhancements (enh). Let the moderators know which section you're working in so that they can be sure everything gets covered.
- To confirm the bug, follow these steps:
- Do some bugzilla searching first to see if the bug might be a duplicate of an existing issue. If it is a duplicate, please add a comment stating the existing bug that this is a duplicate of, and include your IRC nickname. Also, let a moderator know in the channel, so that they can change its status to DUPLICATE.
- Attempt to perform the steps reported using a nightly build from above. Be certain that you can reproduce the bug using the nightly build.
- If you were able to reproduce the bug in the last step, then add a comment to the bug containing detailed steps on how you confirmed the bug. Be certain to include the buildID of the nightly (see table below), your operating system, the steps you followed, your IRC nickname (for Test Day tracking), and any other information that might be pertinent to the developer when they attempt to fix it.
- If you have bugzilla priviledges, please move the bug to the "New" state, if not, alert one of the moderators and they will do it for you.
There is more information about confirming bugs here.
Build ID for October 31 Test Day -------------------------------- OS | Sunbird | Lightning Linux | TODO | TODO Mac | TODO | TODO Windows | TODO | TODO
To Verify Fixed Bugs:
- Select a bug off of this list to verify.
- Attempt to reproduce the bug using the operating system that the bug was reported in.
- If you cannot reproduce the bug, please mark that with a comment in the bug (be sure to include your IRC nickname), and let the moderators know in the channel that you believe the bug to be fixed.
- If a bug has been sufficiently tested on the operating systems that it was reported on, please mark the bug as VERIFIED, or ask one of the moderators of the channel to do that for you.
BUG FOUND!
- In the process of working with the Bugzilla bugs, you may find another bug. When you think you've found a bug, try to reproduce it. Restart Sunbird/Lightning and do the same steps again. The most valuable bugs are those that can be reproduced.
- Once the bug has been reproduced, search for it or something similar on Bugzilla. This can easily be done by searching for the error message, window name, or some other identifying feature of the bug. If you found an existing bug that is just like the bug you found, read the comments. Maybe your situation is slightly different and your input could help developers find the origin of the bug.
- If you can't find the bug in Bugzilla, talk about it in the channel. Maybe others can confirm your bug or find a similar bug in bugzilla. This also gives moderators a chance to guide you to either provide more details, update an existing bug or file a new bug.
- If you are certain you found a unique bug and have read the Bug Writing Guidelines and Bugzilla Etiquette, go ahead and file the bug in Bugzilla. Remember to be as specific as possible.
Rewards!
Mozilla store gift certificate
Scoring
The number of points awarded for each action changes based on the focus of the day. For this day, it will work like this:
- You will get 2 points for each bug confirmed
- You will get 2 points for each bug verified
- If you find a new bug, you will get 1 point. (This is a low number because the focus of the day is on confirming and verifying bugs).
Where do I start?
- Connect to IRC
- Join the #calendar-qa channel
- In the channel,
- Let the moderators know what area you will be confirming bugs in. See the testing instructions for available areas. If you have questions about a bug or if you run into problems, please let a moderator know.
Who will be moderating the #calendar-qa channel on the Test Days?
The moderator's nicks for this test day will be:
- ctalbert
- xFallenAngel
calbot Instructions
xFallenAngel has created a bot to keep track of Test Day progress. It is in its early stages, but it should provide basic functionality. You will be greeted by this bot upon entering #calendar-qa. Be sure to prefix everything you say with "calbot:" so the bot knows you are talking to him.
The commands are based upon natural language. You can for the most part talk to him, as if he were human. If calbot does not want to understand you, try rephrasing your question. If all fails then a moderator will probably be around to help you or you can consult the help. (Try "calbot: help Testday")
Note also, in some cases it is enough to answer with yes or no. This of course should still be prefixed with the bot's name.
Some common phrases:
- Whats going on?
- What can I work on?
- I want to work on <Complete task name>
- I want to do something else
- I am finished
- Who is working on <Complete task name>
Where do I find Bugzilla?
- Bugzilla can be found at http://bugzilla.mozilla.org/
- A list of Calendar specific bugs (without enhancements) can be found here
- A list of already filed enhancement requests can be found here
Tips:
- Make sure you enter the correct information for your platform, version of Thunderbird, Lightning etc. Please include the full build identifier (i.e Thunderbird 1.5.0.7 (20060909) with Lightning 0.3 (2006100206)).
- Be sure to read the Testing Instructions above before filing a bug.
- Feel free to ask on IRC if you need help or have any more questions.
How do I send feedback?
Please use email us at dev-apps-calendar at lists.mozilla.org to send feedback about how the testday went, any overall thoughts about Sunbird and Lightning, and to follow up on issues found and bugs filed. We really appreciate your help today and your feedback is very valuable.
