Calendar Weblog

Yesterday we had a pretty interesting developer conference call, which was basically about the issue that only a very small team is currently developing on Lightning and Sunbird (basically just three people), that it is hard to reach community expectations with regards to bugfixes and feature work with so small a team and what would be necessary to attract more outside developers.

From my point of view one of our shortcomings in the past has been on the communication front. With that I don't mean the communication between different people on certain bug characteristics or code issues (that works great), but the communication between the calendar project and our community.

Currently our channels of communication are:

• This blog, which just gets a post every one to two weeks with a bug fix status update
• our developer and support newsgroups (mozilla.dev.apps.calendar and mozilla.support.calendar), which are not exactly buzzing with activity
• IRC, which not many people are watching

The result - at least as far as I see it - is that

• the core people from the project come across as a closed circle to which it is hard to get in to (the opposite is true)
• what's going on in the project is not exactly transparent. Instead I would call it opaque.

So what can we do to improve our situation, to make the project more transparent, to raise the interest in the project and by that to gain more outside contributors? A few things come to my mind:

• We need to talk more about what we are doing. Therefore every core contributor will try to commit himself to at least blog about various stuff at least once a week from now. These posts will probably range from developer-oriented topics (interesting or disgusting pieces of code, recent bugfixes, UI considerations, QA problems/successes/challenges) and project-related topics (PR issues, community relations, ...) to basically anything that the people find worthwhile to blog about.
  In my opinion a great example to follow here is the Firefox community. Where nearly everybody involved in the project (developers, build engineers, QA staff, PR and marketing people, management) tries to blog regularly about various Firefox stuff or other stuff that interests them. The outside image that this creates is the image of a beehive, where everybody is doing lots of stuff to improve Firefox and in my opinion stuff like this also attracts outside people, because everybody would like to contribute to a project that is alive and well instead of a project that is stalling or dead.
• We need to raise the awareness of the project in the outside world. I'll try to contact a few people to get some press contacts, in the hope to do some interviews with some people interested in open source. We hope that this will raise the awareness of Lightning and Sunbird and bring in outside contributors.

Posted by Simon Paquet at 3:48 AM | Permalink | Comments (14)

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

Posted by Calendar QA Team at 11:55 AM | Permalink | Comments (1)

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!

Posted by Calendar QA Team at 2:36 PM | Permalink | Comments (10)

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!

Posted by Calendar QA Team at 3:39 PM | Permalink | Comments (0)

The 0.8 RC1 is available! I know you've been waiting a long time for it, so grab your self a build. Here are the links:

• Lightning 0.8 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)
• Sunbird 0.8 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)

We really need your help to complete the rest of the L10N Checks and the Update testing, as you can see from our Test Plan.

The Update Testing is of special concern to us, because historically this has always been where we have found critical issues in our release candidate builds. So, please take a look. Feel free to update the test plan wiki or leave a comment on this post with what you tested, so we can track what has been done versus what is still remaining to do.

The test day today has been a great success, but we need to keep up the intensity and keep pounding on this build. It'd be great if we can make our next RC the final build, but we can only do that if we're sure we found all the issues with this RC.

If you have problems or questions, please drop by #calendar-qa on IRC.

Happy Testing!

Posted by Calendar QA Team at 4:35 PM | Permalink | Comments (38)

• 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!

Posted by Calendar QA Team at 6:13 PM | Permalink | Comments (0)

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!

Posted by Calendar QA Team at 6:49 PM | Permalink | Comments (5)

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.

Posted by Calendar QA Team at 11:18 PM | Permalink | Comments (1)

We identified some areas where we need your help testing both products:

• The unifinder (aka event list) has been partly rewritten, and we have already found (and fixed) some regressions.
• The handling of non-native timezones 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 of the prominent problems, like shifting start and end times in the event dialog and calendar views. We will provide one or more calendar files with non-native timezones for testing on our Test Day Wiki Page.
• Every aspect of task related functionality in Lightning, especially the Task mode.

For testing our new features, the experimental offline cache and initial timezone guessing, please have a look at the Test Day Wiki Page for instructions.

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!

Posted by Calendar QA Team at 11:14 AM | Permalink | Comments (9)

Posted by Simon Paquet at 12:02 PM | Permalink | Comments (2)

Lightning users should pay attention to the new drag&drop-conversion feature, i.e. you can transition items between tasks, events, and emails from one to the other by dragging & dropping them to the matching mode toolbar button. Andreas Treumann created a brand-new set of Litmus testcases for this feature (Lightning FFTs, Subgroup 'Drag and Drop' in Litmus).

We suggest that you try a mix of Litmus and ad-hoc testing this time. 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.

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

Happy Testing!

Posted by Calendar QA Team at 11:09 AM | Permalink | Comments (5)

• Task mode (Lightning only)
• Event list aka unifinder for Lightning
• Seperate Calendar mode menu (Lightning only)
• New alarm dialog
• Alarm indicator icons in the Calendar views
• Backend fixes to improve e.g. timezone handling and tasks

We suggest not to use the rather out-of-date Calendar testcases on Litmus but ad hoc testing. Some of you might ask, how this should work. Ad hoc testing is part of exploratory testing and less formal than you are used to with Litmus. You try to find bugs with any means that seem appropriate, and simply check out the different features. Important things, i.e. bugs, can be found quickly, because it is performed with improvisation. Always have a look at the Error Console (especially before submitting a bug report), there could always be valuable information for our developers.

As usual there are also some fixed bugs that need to be verified.

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

Happy Testing!

Posted by Calendar QA Team at 3:00 PM | Permalink | Comments (7)

In order to review the plans and to parcel out the work, we're going to discuss this at the next two QA Chat IRC meetings. These meetings occur at 17:30 UTC (click to find the time in your zone). The next one will be tomorrow, November 15. And the following one will be November 22.

Several great folks have stepped forward to help out, and we're looking forward to making this a success. If you are waiting for to get involved, then wait no longer! We will have lots of tasks from writing code samples, to writing documentation, to doing publicity.

I imagine that for most people out there, talking and learning about test automation doesn't sound like much fun. We're going to talk more about this when we start doing the big publicity for this event, but I'll let you in on a secret. We're going to be working on XPCShell tests, which are written in JavaScript. We're going to be teaching you what you need to know about JavaScript to be effective.

JavaScript is the heart of anything built on the Mozilla platform. That means that if you've always wanted to learn how to write a patch or an extension for Firefox, Thunderbird, Sunbird, Songbird, Seamonkey etc, then you will need to know JavaScript. This event (and learning by helping us prepare for the event) will help you get some hands on practice with the basics of JavaScript and start you on your way.

So, keep that in mind, we'll be talking about it more in the coming weeks. I hope to see you at the QA Chat in #calendar-qa.

Happy Testing!

Posted by Calendar QA Team at 8:17 PM | Permalink | Comments (2)

While reading LpSolit's article about the number of people fixing bugs on Bugzilla I thought that I should try to do the same for Calendar. Unfortunately this didn't really work as a lot of our fixed bugs were never assigned to the person who developed the fix and that completely screws our numbers.

So I thought of a second-best option: The overall number of bugs fixed per quarter for the last five years (click to enlarge):

What the numbers (and especially the moving average) clearly show is that we've been picking up some serious steam and are more active than ever.

Posted by Simon Paquet at 8:02 AM | Permalink | Comments (8)

We already found three show-stopper bugs, and that's why we had to reschedule the test day from Tuesday to Thursday. The new build is being crafted, and will be ready for us on Thursday. There are three things that must be tested:

• We must spot-check each locale to verify that they display properly (you can do this even if you can't read that language).
• We must make certain the bugs we found (399433, 399616, and 399780) were fixed properly. Note that these were all found by people just like you: you can make a difference!
• We must make certain no new bugs were introduced when those were fixed

We hope to see you on Thursday the 18th in #calendar and #calendar-qa. Come join the excitement and be a part of the 0.7 release.

See you Thursday!

Posted by Calendar QA Team at 10:09 PM | Permalink | Comments (5)

We need your help to deliver a good quality release.

So, join us in #calendar-qa on Tuesday. All the information on the test day is in our usual Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 5:18 PM | Permalink | Comments (5)

In today's nightly build for Sunbird and Lightning, the fix for the "Publishing Events Bug" has landed. This bug has plagued people in 0.5, and we wanted to address it in 0.7. However, fixing it was complicated by how many different ways the bug can manifest itself.

We'd like to ask everyone that's seen this issue to retest their configurations with the latest nightly. This way we can determine if the patch fixed all the issues.

Technical Details

• Bug 387559: Main Tracking bug, event creation fails if server requires authentication for PUT but not GET
• Bug 391383: HTTP authentication doesn't work for world-readable, write-restricted ICS shares
• Bug 380291: Event movement failure on local or remote events
• Bug 390084: ssl problem: checking task on remote calendar return fatal error 0x80040111
• Bug 379498: WebDAV publish not publishing every time.
• Bug 380746: webdav write failure if HTTP AUTH needed for PUT but not GET

Thanks for your help in checking out this issue. If you find a problem, please add a comment to bug 387559. If you find other crazy behavior, please file a new bug. If you have any questions please ask them in #calendar or #calendar-qa on IRC and we'll try to help.

Thanks again for your help and happy Testing!

Posted by Calendar QA Team at 11:21 AM | Permalink | Comments (4)

They agreed to check in next week and make a decision, and the following wager was made.

• If Simon is right, Daniel must buy him a bottle of Single Malt Scotch
• If Daniel is right, Simon must buy him a case of his favorite German beer

The QA team has been watching the state of the project closely, keeping track of blockers and proposed blocking bugs as they are filed. This Tuesday, the QA team is doing intensive testing to gather data on the quality of Lightning and Sunbird. This information will enable the calendar team to make the crucial decision on Wednesday about the 0.7 release.

No one wants to slip the date. That said, we also want to release the highest quality product we can for 0.7, so if we have to take a week or two to ensure that, we will. We need your eyes to help us scrutinize Lightning and Sunbird on Tuesday, September 11. We need your help to ascertain the quality level of both products.

We'll take all the data we generate -- bugs, feelings, observations, etc -- and post them here in a Test Day Findings post. That information will be used in the Wednesday Status call to figure out whether Simon will be drinking Scotch, or Daniel will be drinking beer.

So, join us in #calendar-qa on Tuesday. All the information on the test day is in our usual Test Day Wiki Page. Let's figure out where we're at, and when we're going to release 0.7.

Happy Testing!

Posted by Calendar QA Team at 10:23 AM | Permalink | Comments (13)

One of the most exciting features to land in time for this test day is the resolution to the War On Boxes bug. This means that your events will now take up the entire width of the week and day view area until they collide with another event at the same time. This graphic shows it decently well. For a better view, install the nightly build and come to the test day!

Come out to the test day and celebrate with us as we take the new and improved day and week views through regression testing and bug verification. We hope to see you in #calendar-qa on Tuesday, August 28th. For all the details, please see our Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 5:11 PM | Permalink | Comments (3)

Number One: There will be a QA working session on Monday, August 13th at 13:30 UTC. We'll go through the list of unconfirmed enhancement bugs and discuss them to see what's suitable for the 1.0 release.

Number Two: Our last test day was a success, and we had some first time testers in #calendar-qa. Thank you for contributing to our QA effort. Without you it wouldn't be possible. So, we're holding our next test day on Tuesday, August 14th and hope to see you again. This time we'll try to confirm bugs on our unconfirmed list. It includes checking what other users have reported and possibly creating simpler steps to reproduce the bug. You can find all the information on our Test Day wiki page.

We look forward to seeing you in #calendar-qa on Monday, August 13th and Tuesday, August 14th.

Happy Testing!

Posted by Calendar QA Team at 4:21 PM | Permalink | Comments (2)

Posted by Calendar QA Team at 4:34 PM | Permalink | Comments (3)

The former prototype event dialog has been promoted to be the new standard event and task dialog for Lightning and Sunbird. The developers are interested in feedback and bug reports of the test community to improve the new dialog. Also, the new Lighting "today pane" has landed, and we need your help testing it and the mail/calendar switch.

You can find all the information on our Test Day wiki page. We look forward to seeing you in #calendar-qa and Litmus on Tuesday, July 31st.

Happy Testing!

Posted by Calendar QA Team at 4:09 PM | Permalink | Comments (9)

Also, several user interface improvements have landed in Lightning, including the new mail/calendar switch and the "today pane". Join us to check out the new features and find any regressions these massive landings have caused.

As usual you can find all the information on our Test Day wiki page. We look forward to seeing you in #calendar-qa and/or Litmus on Tuesday.

Happy Testing!

Posted by Calendar QA Team at 10:56 AM | Permalink | Comments (2)

• ICS/WebDav: It seems that most of these problems stemmed from incompatible Limit/LimitExcept statements and a change to our code base that causes writes to fail if authentication is required for PUTs but not GETs. This is best summed up in bug 387559
• ICS/WebDav and CalDav: There are also proxy issues affecting both clients for these server types. The proxy configuration seems to have been recently broken, with various reports stating that it worked in 0.3.1 and that it did not work in 0.3.1. We need further clarification on this issue. This issue is summed up in bug 373439

We were able to track down the first issue to a specific check-in, and that is now being investigated. However, we need to do the same with the proxy issue. If you have a proxy configuration please try out various Lightning nightly builds and see if you can determine the build where the proxy configuration stopped working.

Things We Could Use Help With

• Determine the date the proxy configuration stopped working as mentioned above.
• Look at the list of these new remote calendar bugs, and see if we can duplicate some against others (leave us comments in the bug about your ideas).
• Give us suggestions on how we can improve calendar QA

Thanks very much to everyone that turned out for the test day. And congratulations to Alan Schwartz who won the prize for most creative test.

Happy Testing!!

Posted by Calendar QA Team at 5:22 AM | Permalink | Comments (7)

This test day is going to be different because we're encouraging everyone to get creative with their testing. See if you can help us find out why these events are disappearing. Take a look at Litmus, and see what we tested there, then think about ways to go beyond that. On Tuesday, we'll be giving an award for the most creative and effective test, so be sure to add your test to the Test Day Wiki page.

We've been doing a great job as a QA team, but I think this issue gives us an opportunity to think about how we can improve the quality of Lightning and Sunbird. I don't believe that the only solution is to quit our day jobs and work on this around the clock (although that might work).

I think we can find ways to work smarter, to do more with the time and the people we have. Maybe we should look into automating some of the testing. Maybe we should look at the weak parts of our Litmus test suite and fix those areas. Maybe we need to delve deeper into performance and memory leak profiling.

We have started this wiki page for brainstorming ways to improve every aspect of calendar QA. We're going to take your ideas, prioritize them based on what we need the most before 0.7 and put them onto our revised Calendar QA ToDo list.

We will see you on Tuesday. Get creative, bring us your best tests, and prepare to discover where all those events have gone.

Posted by Calendar QA Team at 7:04 PM | Permalink | Comments (8)

At long last, the 0.5 RC's are ready! We have the Sunbird RC's for all our supported locales as well as the Lightning RC's for all our supported locales AND a Lightning Universal Mac build.

We are truly happy to have this finally done. But, now is where we need your help. We've been in total lockdown for some time on this release, so we think the actual code bits are OK. But, this is the first time that the localizers (and anyone) has seen the localized Lightning builds.

We need your help to verify the localizations

We are holding a Localization test day on Friday, June 1 from 1200 UTC to 0100 UTC. Please drop into the #calendar-qa channel to help us test the localized builds and ensure that we can quickly ship the 0.5 that we have all been waiting for.

Here's where to get your hands on the RC:

• Lightning 0.5 RC 1
• Sunbird 0.5 RC 1

Thanks to everyone who has helped with this release. And, an even bigger thank you to everyone who has waited for us to release it. Thanks!

Happy 0.5!

Posted by Calendar QA Team at 11:03 PM | Permalink | Comments (23)

• 30 people took part
332 tests were run
• 90% coverage in litmus on all tier 1 platforms (Windows, Linux, Mac Intel, Mac PPC)
• 9 non-duplicate bugs found.

First place and the prize of the test day went to ssitter with over a hundred tests run in addition to serving as a moderator on the channel. Ray swept in with a close second at 59 tests and several good bugs. Andreas was on his heels with 54 tests. While these guys may have been in the lead, everyone's contribution helped us achieve 90% test coverage, and that's what I'm so excited about.

Several good bugs were found, but none of them were serious enough to block the release. We are still testing, of course, but so far everything looks good. The team is currently in the process of cutting the release builds which will include a localized Lightning and a universal Mac build of Lightning. No code changes are going in, so once we have the release build built, we will do a localization and functional test day. If we don't find any blockers, we'll release that as 0.5.

We are getting down to the wire, so keep an eye on this blog, the newsgroup, and Mozilla Zine for the announcement about the next test day. I'm going to try to have it on Tuesday, but it entirely depends on when the release is built.

I'm not sure what a virtual round of applause sounds like, but we should give ourselves a hand. This was a magnificent feat! Thanks to everyone that joined the test day effort and helped out. Thanks also to our moderators who in put in long hours to stay awake and available through the day. We couldn't do it without you!

Happy Testing!

Posted by Calendar QA Team at 8:22 PM | Permalink | Comments (12)

All questions about my sanity aside, we need a test day. The last of the 0.5 blocking bugs was fixed by Mr. Goold (thanks very much!). We are going to try to spin up a real release (including locales and everything) for both Lightning and Sunbird. But, even if that doesn't happen by tomorrow, we still need to test the code since these current branch nightlies are going to be the RC.

There will be rewards for this test day! I will announce the winner in this forum after they are announced at the Thursday Calendar QA Chat on May 17.

I know the project has been slipping a bit due to the hectic schedules of the core team, but we are trying very hard to keep it moving forward. The best way for you to help us is to participate in the test days. The regression testing is the last thing we need to do before we release 0.5, so the sooner it's finished the sooner we release. And that's exactly why we need your help tomorrow.

Thanks very much. Happy Testing and Good Luck!

Posted by Calendar QA Team at 10:12 AM | Permalink | Comments (13)

The QA Work Session will take place at 14:00 UTC time in the #calendar-qa IRC channel. The Test Day tomorrow will start at the usual 13:00 UTC, you can always find more information on the test day at our Test Day Wiki.

Every test we run and every bug we verify brings us that much closer to our 0.5 release. Thank you very much for your help. We look forward to seeing you tomorrow in #calendar-qa.

Happy Testing.

Posted by Calendar QA Team at 11:45 AM | Permalink | Comments (6)

Drop by #Calendar-QA and join the bug hunt tomorrow. If you can't make it tomorrow, we hope to see you at some point before the end of the week (Drop in for our QA Chat).

For tomorrow's test day we are going to drive it based on the testing recommendations at our Calendar Todo List. I will put together the standard test day wiki page later today. Thanks for your help.

Happy Testing!

Posted by Calendar QA Team at 7:51 AM | Permalink | Comments (7)

We've had two test days since my last post: one on March 20 and the other back on March 6. Both of these were great days. We had hundreds of Litmus Cases run, found several new bugs. Skuribay won the test day on March 6 and Thorn won the test day on March 20. Congratulations to you both!

Function Testing Begins!

As you can see on our new project calendar, Functional Testing for the 0.5 release will begin on Monday, March 26. We need folks to start running through the FFT (Full Functional Tests) in Litmus for both Sunbird and Lightning builds. Please help us cover as many OS's (windows XP, windows Vista, Mac OS X, Linux flavors etc) as we can on these tests. It is important for us to find as many bugs as we can before the string freeze as possible, so that the localizers have solid builds to work with.

We will be also holding a "Hard Core QA Session". This will be from noon UTC to 16:00 UTC on Wednesday March 28. We'll be working on QA Wanted and QA Discussion Needed bugs, to clear those out. Should we finish that, we'll work on functional testing of some of the newer components and features that have landed.

This is a great chance for folks to drop by and help with some of the core issues of bug triage and deep testing. We'll be holding several sessions like this in the coming days. Working with the QA Wanted and difficult defects will give you insight into how best to track and find issues, which will help you win test days and make the calendar code more robust.

It is time to ensure that we release the best possible product we can for 0.5, and that begins right now. We need to amplify the QA on Calendar. So, turn up your favorite music, download a nightly, and see how badly you can break it. If you find an unreported issue, drop us a bug.

I'll see you in #calendar-qa. Happy Testing.

Posted by Calendar QA Team at 3:25 PM | Permalink

Posted by Simon Paquet at 1:36 PM | Permalink

This is going to be a fast release, and the date that we release 0.5 will depend on how fast Calendar-QA can churn through our testing. To keep us organized with the upcoming test days and the release schedule, we have created the first project calendar for Sunbird/Lightning..

The March 6 Test Day marks the beginning of an exciting drive to release. Even more cool features will be landing in the next few days. We will need everyone's help to ensure that these features land intact, and that they work the way we all want them to. If you've got a day or an hour free, stop by the test day, stop by #calendar-qa. Come help us make the most exciting release for Sunbird and Lightning into something truly spectacular. We'll see you on Tuesday, March 6 at the Test Day.

Happy Testing!

Posted by Calendar QA Team at 6:38 PM | Permalink | Comments (13)

Now, those bugs are fixed, and we have spun the release candidate 2 (RC2) build. This will be the 0.3.1 release build if it passes our final round of testing. So, one more time, we need your help to run through the localization matrix, timezone tests, and the regression testing on the 0.3.1 RC2 build. You can see what needs to be tested on our 0.3.1 RC2 test tracking wiki page. As you run tests, please feel free to update that page with your findings.

Thank you very much. Let's get 0.3.1 out the door!

Posted by Calendar QA Team at 1:41 PM | Permalink | Comments (4)

As a result, we are extending the test day through the weekend. If you have a chance, please take a build and run it through our small suite of Localization tests in Litmus.

I have summarized all the information about where we stand on the test day wiki Using that table, you can determine which builds need to be verified and which have already been done. Localizers, you can use that same table to see if you have any issues you need to fix before we spin release candidate 2. We filed bugs for all the issues we found, and those bugs are listed there.

I am extremely encouraged and excited about your response. Today the #calendar-qa channel broke its own record of 30 people involved during a test day! Please keep it going--we need to get all these localizations tested before we push to the final release.

Thank you very much for your time and energy.

Happy Testing!

Posted by Calendar QA Team at 8:22 PM | Permalink | Comments (7)

We are very close to release of 0.3.1. Please join us for this final push. You can find all the information about the test day here: http://wiki.mozilla.org/Calendar:Current_QA_TestDay

Thanks for your help.

Posted by Calendar QA Team at 8:48 AM | Permalink | Comments (5)

• 2 Test days
• 29 People Involved
• 13 Bugs --> 4 stop ship on 0.3.1
• 341 Tests run! (315 Passed, 22 Failed, 4 Unclear)

This is a massive accomplishment. We also attempted to do some public announcements about the test day, and we owe xFallenAngel and Archaeopteryx thanks for their stellar efforts putting that together. We can thank Damian for the fact that there were only 4 unclear tests on these two test days. Thanks go out to eor who organized the second test day. Thanks to lilmatt and dmose who worked around the clock fixing bugs as fast as we found them. And a huge thank you to all the testers and moderators: andrewaclt, bbbrowning, jminta, beb, maarten, mschroeder, nightrat, skuribay, ssitter, ulf, paulivanov, excessory, matthaeus123, elichak, vanessa, zero_, tiago, frac, tomcat, asztal, mvillalo.

The winner of our test day is pretty new to the calendar-qa project. In addition to some great testing, he has worked to help broaden and build the calendar-qa community. Thank you and congratulations to Archaeopteryx.

As a direct result of all our good work, the February 2nd (tomorrow) build will likely be the 0.3.1 release candidate. So, we are not out of the woods yet. I will be holding a QA Work Session in #calendar-qa on this Sunday and Monday at noon UTC onboth days. Those sessions will go for two or three hours and we will concentrate testing on 0.3.1. Please join me if you have the time. On Monday (Feb.5), we will decide whether or not to hold another Test Day before 0.3.1 is officially released.

Thank you very much for your time and your help. I am happy to see the 0.3.1 release moving as quickly and as smoothly as it has. It couldn't have happened without your support.

Happy Testing

Posted by Calendar QA Team at 3:18 PM | Permalink | Comments (10)

And that is why we need you. We have to do testing on Sunbird and Lightning 0.3.1, and we have to continue our testing on Sunbird and Lightning 0.5 as well. So, we are having two test days next week. Our primary test day will be on January 30th, and a secondary test day will be held on February 1st. Click here for more information on those dates.

To underscore the importance of the January 30th test day, I'm happy to announce that we WILL have a reward for the hard working winner of the test day. It will be a Mozilla Store gift certificate. We will announce the winner of the test day at our QA Chat on February 1st.

If you've been wanting to try out a Mozilla test day, if you've been waiting to get involved, this is the perfect time to jump in. We will need all hands on deck as we release 0.3.1 and move quickly toward 0.5.

Thank you very much for your help. We hope to see you either on January 30th or February 1st, or both!

Posted by Calendar QA Team at 12:51 PM | Permalink | Comments (2)

RESULTS:

• 18 new bugs logged!
• 208 Litmus cases passed
• 19 failed
• 30 marked unclear
• Reported your UI feedback to the Calendar Status meeting.

Join us on #calendar-qa as we announce the winner of the test day at tomorrow's Calendar QA Chat.

Thanks for the help yesterday. Let's keep this momentum as we get closer to the 0.5 release. Mark your calendars for the next test day: January 30. We hope to see you there.

Posted by Calendar QA Team at 9:29 AM | Permalink | Comments (3)

The Test Day will be twelve full hours of Views testing and UI feedback bliss, starting at 13:00UTC on January 16 to 01:00UTC on January 17. You can find more information at http://wiki.mozilla.org/Calendar:QA_TestDay:2007-01-16

We are proud to announce that we will offer rewards again as we get closer to releasing 0.5. We will start with fun rewards first and progress to serious ones as the release nears.

So, whether you log in to give feedback on something or you run a test, we hope to see you in #calendar-qa on January 16.

Posted by Calendar QA Team at 1:10 PM | Permalink | Comments (3)

• 5 new people!
• 6 new bugs!
• 31 Remote calendar Litmus tests ran (2 failed, 1 unclear)

Congratulations to our top two testers: Jallison and Archaeopteryx! This was their first calendar test day and they did an excellent job! We had a lively test day with lots of contributors. Thanks to everyone involved: jayelix, ulf, ssitter, mschroeder, maarten, xFallenAngel, dror, bbbrowning, jminta, lilmatt, archaeopteryx, jallison, sipaq, mvl, setr, fopper, mechtilde, and damian. Come join us for our next test day on January 16.

Posted by Calendar QA Team at 12:00 PM | Permalink | Comments (8)

We wish you a happy new year, and we can't think of a better way to kick off 2007 than spending a few hours working with your favorite calendar project. We hope to see you on January 2nd.

For dates, times, details, and all of that, please turn to our ever faithful wiki page: http://wiki.mozilla.org/Calendar:Current_QA_TestDay

-- Calendar QA Team

Posted by Calendar QA Team at 1:10 PM | Permalink | Comments (10)

• 35 Litmus Test Cases Run
• 3 New Bugs Found

Due to the lack of advance notice, we had a very light test day. However, the folks who attended did very good work. We will have another "Remote Calendar Test Day" because remote calendars still need quite a bit more testing. Thanks to everyone that participated: Ulf, Andreas, Ssitter, xFallenAngel, Omar_public, Jminta, Lilmatt, UnLoGiC, Mechtilde, Ghoulio, Ogirtd, TFDuesing, Maarten, and Dmose.

Our next test day will be January 2nd. My new year's resolution will be to make our test days more interactive and more fun. I'm currently brainstorming ways to do that, and I welcome any ideas you may have. If you've got an idea, please post it in a comment to this thread. I will post my ideas once I organize them, so you can see them and send me suggestions.

I look forward to seeing you in the new year as we drive toward our next release of Sunbird and Lightning in early 2007. Please have a happy holiday and a wonderful new year's. I'll see you on January 2nd.

Posted by Calendar QA Team at 8:54 AM | Permalink

Please see http://wiki.mozilla.org/Calendar:Current_QA_TestDay for more information.

Thanks,

Calendar QA Team

Posted by Calendar QA Team at 3:32 PM | Permalink | Comments (2)

We ran a complete regression on both Sunbird and Lightning, ensuring that the recent database patch did not have any unintended side effects. We were also able to focus testing energy on the new prototype dialogs that the Sun team has been implementing. I'd like to thank everyone who was involved for their continued (and new) contributions: xFallenAngel, Sebo, Ulf, Andreas, Nightrat, Ssitter, Koenh, Matthaeus123, Fopper, Nor123, Soupes, Mechtilde, Mschroeder, Celina63, Dmose, Jminta, Lilmatt, Sandos.

We also held a mini-test day on December 1st with 22 students from Seneca College in Toronto. In a whirl-wind effort, they confirmed 16 unconfirmed bugs and filed 6 defects in 45 minutes! We are looking forward to working with the Seneca students again next semester.

Our next test day will be December 19. We will dedicate this day to testing the various types of remote calendars that Sunbird and Lightning can use: FTP, CalDav, WebDav, WCAP. As a holiday gift to the entire community, a new remote calendar provider might be available for testing on the 19th. You can either stay tuned for more information on that, or you can get a sneak peak by volunteering to aid with the preliminary smoke-testing of the new provider (assuming it lands). To volunteer, just drop by the #calendar-qa channel.

Thank you very much for the excellent test day on the 5th. We could not do it without you.

See you on the 19th.

-- Calendar QA Team

Posted by Calendar QA Team at 2:44 PM | Permalink | Comments (4)

The Test Day wiki page will be landing today in its normal location.

Remember you can always find ways to help out by checking out our Calendar QA ToDo List

We look forward to seeing you on December 5th.

-- Calendar QA Team

Posted by Calendar QA Team at 8:26 AM | Permalink | Comments (2)

Thanks very much to everyone that helped out, especially Matthaeus123 who ran 173 of those Litmus testcases! Thanks also to everyone that wrestled with the migration wizard code: Sebo, Ssitter, Koen, Unlogic, Nor123, Celina63, Jminta, Lilmatt, Mc, Mat75, and Matthaeus123. Thanks also to xFallenAngel for his calbot bot.

We found several issues in the migration wizard code, and even rebuilt the patch to fix dead-broke issues halfway through the test day. Next time we have a test day focused on brand new functionality, we will ensure the functionality is smoke-tested prior to the test day. We are also going to change the times for the test day so that the day better corresponds to when the nightly builds run. This should help clear some confusion surrounding "which build do I test with". Thanks again to everyone that participated. We're going to take a week off from test days, so we can make these changes. Our next test day will be December 5th. We'll see you on the 5th!

Happy Testing.

Posted by Calendar QA Team at 8:40 AM | Permalink | Comments (5)

The Calendar-QA team plans to celebrate these new features with an entire test day focused specifically on the new functionality, and we'd love for you to join us. The test day will be on November 14, from 01:00 (UTC) to November 15, 00:00 (UTC), that's 23 full hours of testing. For this test day, we will be returning to our Litmus Testing System, so it will be very easy for everyone to contribute. Please refer to the test day wiki for more information.

Additionally, the Calendar-QA team has already begun planning for our next test day. If you'd like to help out with that effort, please drop by the #calendar-qa (irc://irc.mozilla.org#calendar-qa) channel this week and let us know.

We hope to see you in #calendar-qa on November 14th.

Posted by Calendar QA Team at 9:41 AM | Permalink | Comments (2)