Mozilla Calendar Project Blog Its about time for some news…

The test day held on Thursday, June 26th will be the first one in a series of test days and QA working sessions over the next weeks. This time, please help us to find the most hidden regressions. We suggest that you try Litmus and some ad-hoc testing to find regressions in any part of Sunbird or Lightning 0.9pre.

There are also many fixed bugs that need to be verified. You simply have to add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.

Join us in the #calendar-qa IRC channel on Thursday. All the information on the test day is on our usual Test Day wiki page. Happy Testing!

Hope to see you in #calendar-qa!

mschroeder
Calendar QA Team

Our first test day after the release of Lightning and Sunbird 0.8 will be on Thursday, June 5th. Please help us find any new regressions and bugs. We identified some areas where we need your help testing:

• New dialog for modifying & deleting a repeating event
• ‘Switch this calendar on’ feature to disable a calendar completely
• iMIP/iTIP support (email based invitations)
• CalDAV calendar support

We suggest that you try a mix of Litmus and ad-hoc testing. Ad-hoc testing is testing where you attempt to use the product like a “normal user” to find any issues that crop up along the way. You also try to make the program break by doing unexpected things, just do anything you can imagine – mix up events, emails, tasks, calendar types etc. When you find something, take a look at the Error Console (especially before submitting a bug report), since there is usually very valuable information there that points to the cause of the bug.

There are also many fixed bugs that need to be verified. You simply add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.

Join us in the #calendar-qa IRC channel on Thursday. All the information on the test day is on our usual test day wiki page.

Happy Testing!

Our next test day will be on Thursday, March 20th. We will be testing nightly builds before creating a second release candidate for Lightning and Sunbird 0.8, there may even be a RC2 ready for the testday. Please help us find any stop-ship bugs that might still be hiding in both products. There is a ton of stuff to do:
You should have a look at our test plan for the release. If you are a localizer, try the recent builds and check your localized builds of Lightning and Sunbird. Your feedback by editing the table in our test plan is appreciated. We also need help to re-test localized builds with known (but now hopefully fixed) bugs.
We want to test migration from previous releases 0.3, 0.3.1/0.5 and 0.7 to 0.8. For these tests ask in #calendar-qa how to proceed. To ensure basic functionality for the release, general testing with Litmus and ad-hoc methods on all OS’s must be performed.
As usual there are also some fixed bugs left that need to be verified. You simply add a comment to the bug report stating what product, version and operating system you used while verifying the bug was fixed.
Join us in the #calendar-qa IRC channel on Thursday. All the information on the test day is on our usual test day wiki page, and on the test plan.
Happy Testing!

We are getting extremely close to the RC for 0.8, in fact we might even have the first release candidate on the test day. So, everybody come on out and help us out. In particular, we could use some help with:

• Upgrade testing from previous releases (0.3.1, 0.5, 0.7) to 0.8
• Time zone support
• Task Mode Ad-Hoc testing
• Locale Testing (if we have localized builds available)
• General Testing with Litmus and Ad-Hoc methods

All the relevant information is up at the test day wiki page, and on the test plan. We hope to see you in the #calendar-qa IRC channel on Thursday March 6!

Onward to 0.8!

Our next test day will be on Thursday, February 21st. It will be the
final test day in preparation for the first release candidate of
Lightning and Sunbird 0.8. We need your help to test some crucial
features in both products.

The handling of time zones in Sunbird and Lightning has greatly improved,
and you should be able to import and subscribe to calendars created with
other calendar applications without any problems. We also updated our
internal time zones according to the recent official changes. You can
test the functionality using calendars (also created with other
software), and checking if the events and tasks are shown at the correct
times in the calendar views and task list.

The new Task mode with its own toolbar in Lightning is one of the
prominent features for the upcoming release. Please have a look at this
feature, and try it out as extensively as possible.

When testing the experimental offline support and initial timezone guessing, please have a look at the Test Day Wiki Page for instructions. We are particularly interested in your experiences using the experimental offline support, whether positive or negative. Please add a comment to the end of the ‘What specifically will we be testing?’ section of the Test Day Wiki Page.

Our last test day has been a great success, especially the number of
Litmus testcases run. Andreas Treumann used the feedback on unclear and
broken testcases to improve those, and our testcases should be more
up-to-date now.

We suggest that you try a mix of Litmus and ad-hoc testing. Ad-hoc
testing is testing where you attempt to use the product like a “normal
user” to find any issues that crop up along the way. You also try to
make the program break by doing unexpected things, just do anything you
can imagine – mix up events, emails, tasks, calendar types etc. When you
find something, take a look at the Error Console (especially before
submitting a bug report), since there is usually very valuable
information there that points to the cause of the bug.

As usual there are also some fixed bugs that need to be verified.
You simply add a comment to the bug report stating what product, version
and operating system you used while verifying the bug fixed.

Join us in #calendar-qa on Thursday. All the information on the test day
is on our usual Test Day Wiki Page.

Happy Testing!

In our last QA Chat, we decided to revive our old tradition of blogging about the test day results. So, on our last testday we had really great participation from a whole host of folks, and four of these intrepid individuals burned through our Litmus tests, running 313 tests. Overall, 6 new bugs were found. Congratulations to thetux for taking the cup with a whopping 210 tests run!!

We are continuing to push on toward the 0.8 release candidate. In that vein, I’d like to make a special plea for testing. We are about to check in the code that will update the time zone database. Once that happens, we need you to do two things:

• TEST: We could really use your help in testing this. You know your own time zone far better than we do, so make sure your calendar switches into and out of summer time (or doesn’t switch at all) at the appropriate dates for this year.
• BACKUP:If you have been running the 0.8 nightly builds, then you MUST backup your local (non-network) calendars (export them to ICS) BEFORE upgrading to a build with this change in it. The details are in bugzilla, but if you are running some of the 0.8pre builds, then this change might break your calendar when you update to the latest nightly.

What if I am running 0.7 (or earlier)? In that case, you are fine. You should be able to upgrade to 0.8 with no problems. Of course, it is always a good idea to periodically backup your calendars anyway. This issue occurs because we don’t support upgrades between nightly versions, only between released versions of the software.

That said, we know a number of early adopters have already made the switch to 0.8pre builds and we want them to be aware of this potential issue.