- 1 When is the test day?
- 2 Where do I start?
- 3 OK, I am in the channel, now what?
- 4 Who will be moderating the #calendar-qa channel on the Test Days?
- 5 What build should I test?
- 6 What specifically will we be testing?
- 7 BEFORE YOU START--BACKUP YOUR PROFILE
- 8 Testing Instructions
- 9 Where do I find Litmus and Bugzilla?
- 10 How do I send feedback?
- 11 Thanks!
When is the test day?
- The test day will run from 13:00 UTC on February 7th 2008 to 01:00 UTC on February 8th 2008. The test day will start exactly when the nightly builds are available and will end 8 hours later. We realize that this may not be optimal for all our testers, so if there is great demand, we will extend the ending time.
- Find the starting time in your timezone
- Find the ending time in your timezone
Where do I start?
- Open up your favorite IRC client:
- Connect to irc.mozilla.org
- Join the channel #calendar-qa
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:
What build should I test?
We will be testing the latest nightly builds of Sunbird and Lightning:
Lightning (for Thunderbird 3.0b2pre):
What specifically will we be testing?
- Unifinder (aka event list) - has been partly rewritten, and we have already found (and fixed) some regressions. We need more testing to ensure it is ready for 0.8.
- Handling of non-native timezones - has greatly improved, and you should be able to import and subscribe to calendars created with other calendar applications without any of the prominent problems, like shifting start and end times in the event dialog and calendar views. You can find calendar files with non-native timezones for testing subscribe, import, and export functionality here: http://mozilla.x-home.org/ics/
- Task related functionality in Lightning, especially the Task mode.
- Testing experimental offline cache - for WCAP and ICS calendar only. You can enable the offline cache in the calendar properties dialog. Don't forget to restart after enabling. We have already found a critical bug, bug 412914. Please read before testing, and don't forget to backup your profile (see below)!
- Testing initial timezone guessing - Don't forget to backup your profile (see below)! First you have to remove the saved preference for calendar.timezone.local from prefs.js, otherwise the initial timezone guessing is not called. Then you should test if Sunbird or Lightning detects the correct timezone matching your OS timezone on start. Likely timezones are also determined by the locale of Sunbird or Lightning. Please report any mismatches and problems to bug 413265.
- Ad hoc testing - Try to find bugs with any means that seem appropriate, and simply check out the different features (e.g. the event list aka unifinder). Always have a look at the Error Console (especially before submitting a bug report), there could always be valuable information for our developers.
- Litmus testing - Run our Litmus testcases. Have a look at the testing instructions for details.
- Verify Fixed Bugs - There is a list of bugs fixed since the release of 0.7, that have to be verified fixed on different operating systems. Add a comment with details of used Lightning or Sunbird version, operating system and if the issue was really fixed to the bug report.
BEFORE YOU START--BACKUP YOUR PROFILE
Though we don't expect things to go wrong, we always strongly encourage you to back up your profile and to do your testing on a "test" profile.
Backing up a profile is easy:
1. Find your profile directory:
|OS||Thunderbird Profile||Sunbird Profile|
2. Copy the root of it somewhere else, for example copy the Thunderbird or Sunbird directory and everything below it.
Creating a testing profile is also easy:
- Launch your application with a -P option (from a terminal prompt)
- Create a new profile by clicking the 'Create Profile' button
- Click 'Next', Give it a name like "Testing Profile", Click 'Finish'
- Select the testing profile, and click the 'Start Calendar' (Or 'Start Shredder' in Thunderbird) button.
Remember that you will have to start the application with the -P option during testing so you can pick your testing profile
Once you've finished testing, you can delete the extra profiles and you'll be back to normal. If something goes terribly wrong (although we don't expect it to), close the application and just replace the profile with the backed up copy. That will reset the application to the way it was before you started testing.
To Run Litmus Test Cases
Build ID Test Day -------------------------------- OS | Sunbird | Lightning Linux | 2008020619 | 2008020618 Mac | 2008020622 | 2008020621 Windows | 2008020619 | 2008020618
- Download Sunbird or Lightning from the above URLs
- Create your testing profile (see above)
- Go to Litmus.
- Select Run Tests, the Product is Calendar. Your buildId should match the one in the table above. Verify that it does. Sunbird's buildId is in the "About Sunbird" window. Lightning's buildId is in its description in the Add-ons Manager.
- Choose a Test group and subgroup to test on. If you are running the lightning-wcap extension, please run the "Prototypes" and "WCAP Calendar" tests prior to other tests.
- Follow the test steps and verify the function under test works as described in Expected Results.
- If the test case performs as expected, mark it as a "Pass". If not, mark it as a "Fail" and then enter a bug (see below).
- When you've finished one test, go to the next test by clicking the test case name.
- Once you've completed all the tests in a group, click the "Submit All Results" button at the bottom.
- In the process of working with the Bugzilla or Litmus, 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.
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 to help the better!
- Consider looking at the Calendar ToDo list, there is much you can help with.
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
- Make sure you enter the correct information for your platform, version of Thunderbird, Lightning etc. Please include the full build identifier (i.e Thunderbird 22.214.171.124 (20070326) with Lightning 0.8pre (2008020504)).
- 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.
Thanks so much for your help. We could never do this without you.