Calendar:QA TestDays: Difference between revisions
Line 10: | Line 10: | ||
Thank you for participating in this test day. The success of Sunbird and Lightning is heavily dependent on community members like you. We appreciate your support! | Thank you for participating in this test day. The success of Sunbird and Lightning is heavily dependent on community members like you. We appreciate your support! | ||
When you are done, please send feedback to | When you are done, please send feedback to dev-apps-calendar@lists.mozilla.org. We are very interested to hear about how the test day went, any overall thoughts about the Calendar project, and roll up of issues found and bugs filed. | ||
The official time for the test day is '''Tuesday, August 22, 2006, from | The official time for the test day is '''Tuesday, August 22, 2006, from 12:00PM UTC to 2:00AM UTC, but anyone can jump on at any time on any day! | ||
''For more information about this release, please check out the [[Calendar:Home_Page| Calendar Home Page]]. You will find the current release status, and more general information on the Calendar project.'' | ''For more information about this release, please check out the [[Calendar:Home_Page| Calendar Home Page]]. You will find the current release status, and more general information on the Calendar project.'' |
Revision as of 15:49, 15 August 2006
This is a draft
This is the first version of this page. It contains a lot of TODO markers that need to be changed. My english might also not be the best, go ahead and read through it to remove commas, make first letters of Nouns lowercase, or other problems that might lead back to my german origin :P
This page was taken from the Bon Echo test day site. A lot of text is identical. If this is not desired, go ahead and change it.
--XFallenAngel 01:04, 11 August 2006 (PDT)
Welcome to the Calendar Community Test Day!
Thank you for participating in this test day. The success of Sunbird and Lightning is heavily dependent on community members like you. We appreciate your support!
When you are done, please send feedback to dev-apps-calendar@lists.mozilla.org. We are very interested to hear about how the test day went, any overall thoughts about the Calendar project, and roll up of issues found and bugs filed.
The official time for the test day is Tuesday, August 22, 2006, from 12:00PM UTC to 2:00AM UTC, but anyone can jump on at any time on any day!
For more information about this release, please check out the Calendar Home Page. You will find the current release status, and more general information on the Calendar project.
FAQ
Where do I start?
- Open up your favorite IRC client:
- Connect to irc.mozilla.org
- Join the #calendar-qa channel
OK, I am in the channel, now what?
Let the moderators know if you have any questions or encounter any problems. If you are not familiar with our bugzilla bug tracking system, feel free to report your problems to a moderator and they can log any bugs for you.
Who will be moderating the #calendar-qa channel on the Test Days?
The moderator's nicks for this test day will be:
- ctalbert
- jminta
- ...
- TODO: insert correct moderators here
What build should I test?
We will be testing the Sunbird and Lightning nightly candidate builds:
Sunbird: ftp://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk
Lightning (Thunderbird 1.5.x): ftp://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8
Lightning (Thunderbird 1.6 - 3.0): ftp://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-trunk
What specifically will we be testing?
TODO
Testing Instructions
Follow these instructions:
- Download Sunbird or Lightning from the above URLs
- Use it. Try to do everything an end-user might do, ranging from simple calendar operations to power user features. Try to think of actions that are not typical like (TODO: something wierd that has caused a bug in the past, maybe with a link to bugzilla) since you will most likely find a bug there.
- Look for that bug or something similar on Bugzilla. This can easily be done by searching for the error message, window name, or some over identifing 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.
- Try to reproduce the Bug. Restart Sunbird/Lightning and do the same steps again. The most valuable bugs are those, that can be reproduced.
- 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 the Bugzilla Etiquette go ahead and file the bug in Bugzilla. Remember to be as specific as possible.
Some other ways you can help:
- Think of some test cases that aren't already included in Litmus (we love suggestions!).
- Ask your friends to join you. The more people help the better!
Where do I find Litmus and Bugzilla?
- Litmus can be found at http://litmus.mozilla.org/
- A List of Calendar specific test cases can be found via the search function
- 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.5 (20060719) with Lightning 0.1+ (2006080907)).
- 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.
- TODO: Put in the Build ID for sunbird since people can't just find it.
- When running tests in Litmus, wait to submit all the tests as one batch (use the submit button at the bottom of the test list).
- When running tests in Litmus, click on the test name to go to the next test, not "View Test".
- TODO: come up with an idea on how to achieve the most test coverage. Perhaps we can talk to people about what tests they'd like to run and suggest certain areas. Or perhaps we can encourage them to do ad-hoc testing. We could have some kind of goal regarding the "Personal Testing Coverage" and the "Community Testing Coverage" metrics from the Litmus run tests page. Other thoughts?
How do I send feedback?
Please use the (TODO: email) to send feedback about how the testday went, any overall thoughts about Sunbird and Lightning, and roll up of issues found and bugs filed. We really appreciate your help today and your feedback is very valuable.
Rewards for this Test Day
- The top 2 testers will each earn a $25 gift certificate to the Mozilla Store!
- As always, know that we appreciate your support and you have our heart felt gratitude. And really, what could be better than that?