Calendar:QA TestDay:2006-11-14

From MozillaWiki
Jump to: navigation, search

<< Back to Calendar QA TestDays

RESULTS!

  • 179 Litmus cases run
  • 1 Migration wizard utterly pounded
  • 1 new test day bot beta

We had a good turnout and good testing on the test day. Thanks very much to matthaeus123 for an amazing 173 Litmus testcases run! Thanks to everyone that pounded the migrator code: nor123, koen, unlogic, mat75, matthaeus123, sebo, and ssitter. Thanks to xFallenAngel for creating our new test day helper bot, calbot. We're still ironing out the bot's features but in the future the bot will help keep track of things during test days.

We found several issues with the migration wizard, and learned several valuable lessons. We're going to move the test day start time so that it coincides better with the nightly build. We're also going to ensure that any new functionality we test will be at least smoke tested before the test day. As always your suggestions are welcome.

Thanks again.

When is the test day?

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:

Sunbird:

http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk/

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/

What specifically will we be testing?

We will be working on migration and testing the advanced panel in the preferences dialog, along with standard Litmus and Usability testing.

We need to:

  • Use the migration wizard to attempt to execute the following matrix:
Migrate From                        Migrate To
Thunderbird + Calendar Extension    Thunderbird + Lightning
Firefox + Calendar Extension        Thunderbird + Lightning
Sunbird 0.2                         Sunbird
Apple iCal                          Sunbird
Apple iCal                          Thunderbird + Lightning
Gnome Evolution                     Sunbird
Gnome Evolution                     Thunderbird + Lightning

You can also mix and match these because the Migration wizard should be able to support migrating from multiple sources. We need to test each of these on Windows, Linux, and Mac, because the profile directories are different on these operating systems.

To use the migration wizard, you will have to install the most recent nightly builds (20061114). (Currently not available for Mac). The migrator is triggered as soon as there are no calendars in your profile. That is either a new profile, or for testing you could also delete all your current calendars in your testing profile to trigger the migrator again.

If the migrator fails to import your test data, please try to determine which ICS it was importing, and file that with your bug. Don't forget to search for a bug that might have been filed earlier in the test day.


Enabling migration debugging

If you encounter any problems with migration, you can turn on additional debugging code, which may give more information useful to fix the error. To do this:

  1. Open Options/Preferences (The name and location will vary based on your OS.)
  2. Go to Advanced
  3. Open the Config Editor
  4. Create a new boolean pref named calendar.migration.log and sets its value to true.
  5. Re-try your migration. Additional information will now be reported in the Error Console (under Tools).

Links to old software

Other Areas You Could Help With

  • Confirm unconfirmed bugzilla bugs - ensure that the bugs are reproducible and not duplicates of known issues
  • Verify existing fixes - ensure that the fixes did fix the problem in the bug report and did not cause other regressions
  • Investigate defects that are flagged as QAWanted - provide more details, analysis, and clearer or simpler steps to reproduce the issue.

If you've already backed up your profile, you can skip directly to the Testing Instructions area.

BEFORE YOU START--BACKUP YOUR PROFILE

Once you have downloaded the version of the application you want to test, but before you start it, you MUST back up your profile and create a testing profile, otherwise, you run a very good chance of losing your data.

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 November 14 Test Day
--------------------------------
OS      | Sunbird    | Lightning
Linux   | 2006111406 | 2006111406
Mac     | 2006111209 | 2006111211
Windows | 2006111407 | 2006111406
  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. We would like to have lots of focus on the migration wizard and the printing subsystem. Please be sure you perform those Litmus cases first before moving on to other Litmus cases.
    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:

  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 privledges, 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.


BUG FOUND!

  1. 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.
  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 help the better!

Where do I find Litmus and 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.

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>
Retrieved from "https://wiki.mozilla.org/index.php?title=Calendar:QA_TestDay:2006-11-14&oldid=42395"