Confirmed users
3,816
edits
Calendar:QA TestDay:2006-10-03: Difference between revisions
→'''RESULTS!'''
m (add Build IDs for Lightning) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<small>[[Calendar:QA_TestDays|<< Back to Calendar QA TestDays]]</small> | <small>[[Calendar:QA_TestDays|<< Back to Calendar QA TestDays]]</small> | ||
<font size=6 color=red> | |||
= '''RESULTS!''' = | |||
* '''1 ShowStopper Bug''' | |||
* 159 Tests Ran in Litmus! | |||
* 5 New Bugs! | |||
* 7 Fixes Verified! | |||
</font> | |||
Many, many thanks to everyone involved. The test day was a success--we did a ton of good testing with far fewer people than our last test day. Special thanks go to the good people at [http://www.linpro.no/ Linpro AS] (rogerk and jamesb) for sponsoring our test day awards. Thanks to everyone who stepped up to help out with moderating this test day: ssitter, xFallenAngel, lilmatt, dmose, jminta. Thanks to Celina63 for architecting our Test Day wiki page. | |||
Thanks also to all the new contributors we had this test day: TedBullock, omar_public, Mc, matthaeus123, karora. | |||
I continue to be impressed by the expertise and professionalism exhibited by the Calendar Community. You should all pat yourselves on the back. We hope to see you all soon for our next test day. And don't forget to check out our weekly [http://wiki.mozilla.org/Calendar:QA_TODO Calendar-QA ToDo list] | |||
Our Stars: | |||
{| border=2 cellpadding=2 | |||
|- | |||
| jminta || lilmatt || dmose | |||
|- | |||
| celina63 || xFallenAngel || Mc | |||
|- | |||
| bbbrowning || karora || mschroder | |||
|- | |||
| rogerk || sebo || lonelybob | |||
|- | |||
| nightrat || Taliesin || ssitter | |||
|- | |||
| omar_public || matthaeus123 || excessory | |||
|- | |||
| TedBullock || worzel || Damian | |||
|- | |||
|} | |||
'''And now...the winners!''' | |||
* 1st Prize goes to Sebo for finding the show stopper {{bug|355304}}! | |||
* 2nd Prize for running 45 test cases in Litmus goes to karora! | |||
Thanks again everyone! | |||
== Where do I start? == | == Where do I start? == | ||
| Line 7: | Line 45: | ||
** [http://www.ircreviews.org/clients/platforms-macos.html MacOS clients] | ** [http://www.ircreviews.org/clients/platforms-macos.html MacOS clients] | ||
** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients] | ** [http://www.ircreviews.org/clients/platforms-unix.html Linux clients] | ||
** [https://addons.mozilla.org/firefox/16/ ChatZilla (Firefox extension)] | ** [https://addons.mozilla.org/firefox/16/ ChatZilla (Firefox extension)] | ||
* Connect to [irc://irc.mozilla.org irc.mozilla.org] | * Connect to [irc://irc.mozilla.org irc.mozilla.org] | ||
* Join the #calendar-qa channel | * Join the #calendar-qa channel | ||
== OK, I am in the channel, now what? == | == OK, I am in the channel, now what? == | ||
| Line 108: | Line 145: | ||
'''BUG FOUND!''' | '''BUG FOUND!''' | ||
# 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. | # 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 | # Once the bug has been reproduced, search for it or something similar on [https://bugzilla.mozilla.org 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 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 [https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html Bug Writing Guidelines] and [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette], go ahead and file the bug in Bugzilla. Remember to be as specific as possible. | # If you are certain you found a unique bug and have read the [https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html Bug Writing Guidelines] and [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette], go ahead and file the bug in Bugzilla. Remember to be as specific as possible. | ||
| Line 135: | Line 172: | ||
== Rewards! == | == Rewards! == | ||
There will be one prize available for the person that makes the largest contribution to the test day. That can be done by verifying bugs, finding bugs, and/or running Litmus testcases. Each of these endeavors will be scored equally, so the more you do, the more likely you are to win! | |||
Rewards are provided by [http://www.linpro.no Linpro!] | |||
I only know most of you by your IRC nickname, so to ensure your bugzilla activity gets counted, be certain to email cmtalbert at gmail dot com with your bugzilla user ID. Please use "TEST DAY" in the subject line of the mail. | |||
*As always, know that we appreciate everyone's contribution and you all have our heart felt gratitude. Thank you. | *As always, know that we appreciate everyone's contribution and you all have our heart felt gratitude. Thank you. | ||