Calendar:QA TestDay:2006-12-05

From MozillaWiki
Jump to: navigation, search

<< Back to Calendar QA TestDays


  • 151 Litmus Test Cases Ran!
  • 20 bugs logged!
  • 17 test cases failed, 4 found to be unclear

We had a very successful test day on December 5th. We were able to run a good regression of tests against Sunbird, and found no serious issues with the recent database migration. We also took a hard look at the new prototype dialogs, and logged several bugs against them. Thanks to everyone that participated: xFallenAngel, Sebo, Ulf, Andreas, Nightrat, Ssitter, Koenh, Matthaeus123, Fopper, Nor123, Soupes, Mechtilde, Mschroeder, Celina63, Dmose, Jminta, Lilmatt, Sandos.

We had a great turnout, and great testing. We look forward to seeing you all on December 19th. December 19th will be a remote calendar test day, testing all the various ways to work with remote calendars.

If anyone would like to help us in the meantime to get ready for that test day and by triaging some of the Litmus failures and unclear test cases, please drop by the #calendar-qa channel and let us know.

Thanks again for all your hard work! You are making a huge difference in the quality of the Calendar Code!

When is the test day?

  • The test day will run from 13:00 UTC on December 5th to 1:00 UTC on Dec. 6th. These are new times. The test day will start exactly when the nightly builds are available and will end 12 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?

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
  • ssitter
  • lilmatt
  • dmose
  • xFallenAngel
  • sebo
  • jminta

What build should I test?

We will be testing the latest nightly builds of Sunbird and Lightning:


Lightning (for Thunderbird 1.5.x and 2.0 candidates):

  • Note: For the Sun dialogs load the lightning-wcap.xpi from the subfolder for your Operating System in the directory below.

What specifically will we be testing?

An internal database upgrade was made. We need to be very certain that this has caused no unseen regressions. Running our old Litmus tests is an important step in this. We also need to run migration tests from releases to the current nightly (the database will auto-upgrade - this does not involve the migration wizard).

  • On Sunbird, we will run litmus regressions, confirm unconfirmed bugs, and hunt new bugs.
  • On Lightning, we will be testing the new Sun provided dialogs. The Litmus tests for these will be in the testgroup called "Lightning Full Functional Tests (FFT) and in the Subgroups: "Prototypes" and "WCAP Calendar"


Due to a recent SQL Database change you CANNOT test this nightly on any profile that was created prior to Nov. 29. If you attempt this, your database will be automatically upgraded.

Therefore, we strongly recommend you create a new profile data for testing.

Backing up a profile is easy:
1. Find your profile directory:

OS Thunderbird Profile Sunbird Profile
Windows  %AppData%\Thunderbird  %AppData%\Mozilla\Sunbird
Linux ~/.thunderbird ~/.mozilla/sunbird
MacOSX ~/Library/Thunderbird ~/Library/Application Support/Sunbird

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:

  1. Launch your application with a -P option
  2. Create a New Profile by clicking the Create a New Profile button
  3. Click Next, Give it a name like "Testing Profile", click Finish
  4. Select the testing profile and click the "Start Calendar" (Or Start Mail 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.

Testing Instructions

To Run Litmus Test Cases

Build ID for December 5 Test Day
OS      | Sunbird    | Lightning
Linux   | 2006120503 | 2006120503
Mac     | 2006120504 | TODO
Windows | 2006120503 | 2006120503
  1. Download Sunbird or Lightning from the above URLs
  2. Create your testing profile (see above)
  3. Go to Litmus.
    1. 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.
    2. 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.
    3. Follow the test steps and verify the function under test works as described in Expected Results.
    4. 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).
    5. When you've finished one test, go to the next test by clicking the test case name.
    6. Once you've completed all the tests in a group, click the "Submit All Results" button at the bottom.

To Confirm Unconfirmed Bugs:

We need help confirming bugs in Bugzilla. We currently have 252 unconfirmed bugs. Can you help confirm some? If you need privileges, please let a moderator know and we will try to help with that.

  1. Click on a Bugzilla query below for a component that you would like to work on.
  1. Pick a bug that sounds interesting, and tell one of the moderators in the channel that you're working on it. (They will let you know whether or not someone's already taken it).
  2. To confirm the bug, follow these steps:
    1. 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.
    2. Attempt to perform the steps reported using a nightly build from above. Be certain that you can reproduce the bug using the nightly build.
    3. 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.
    4. If you have Bugzilla privileges, 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.


  1. 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.
  2. 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.
  3. 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.
  4. 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?

  • Bugzilla can be found at
  • 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 (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 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.

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 TestdayGreeting")

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>


  • There will be no rewards available for this test day. We're saving our resources for test days when we are closer to a release :-)
  • But as always, thank you VERY VERY much for helping us out. We definitely couldn't do this without all of you!
  • That said, if you or your company want to sponsor rewards for a test day, please hop onto IRC and let us know.