Mozilla Calendar Project Blog Its about time for some news…

Join us on Thursday, December 13th for the first testday after the 0.7 release. The developers landed a first set of features for the upcoming Lightning & Sunbird 0.8:

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

Well 0.7 has released, and we have been busy laying the ground work for the Test Automation Summit. We’re ready to expose some of these preparations and plans and get to work on the documentation that we’ll need in order to do the Summit.

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!

Join us on Thursday, October 18th for the 0.7 RC2 test day. Help us determine if there are any show stoppers that should be fixed before we release 0.7.

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

You can read all the details on the Test Day Wiki.

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!

We are in code freeze, and our first Release Candidate (RC1) will be ready soon. We need YOU to find every problem which can stop a release. There also is a long list of bugs fixed since the release of 0.5, that have to be verified fixed on different operating systems. At last almost all l10n teams finished their localizations of Lightning and Sunbird. Now we – but especially native speakers – have to check these language versions for completeness and correctness.

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!

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

More information is of course available in bugzilla. These are the main bugs we are following that track different manifestations of the problem.

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

In our status call on Wednesday, our resident skeptic, Simon, and our optimistic project lead, Daniel, got into a discussion about the 0.7 release date. The date is currently October 15, with an RC1 due on September 17. Simon said that there is no way we are going to make those dates. He cited lots of reasons for that and advocated cutting some features. Daniel remained optimistic, and agreed that some features should perhaps be cut, but we should look closer at it next week. Daniel feels confident that most of the issues will be addressed, and the dates can still be made.

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!

Tons of new features and bugfixes have landed in recent weeks in preparation for the 0.7 release. We will spend the test day this Tuesday, August 28th focusing on verifying these bugs and on regression testing the calendar back-end, alarms, calendar list, and views.

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!

Two events will take place next week at Calendar QA.

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!

Just a quick reminder that we have our Calendar Test Day tomorrow. Please see the Test Day Wiki for more information.