You are currently browsing the archives for the Litmus category.
Rodan, the machine that houses Litmus, failed on Saturday after many years of faithful service.
Zach and Aravind are working to get a new machine or VM setup as a replacement (I’m still on vacation), but Litmus will be unavailable for a little while.
Sorry for any inconvenience.
The Mozilla QA team has setup a Google calendar so it will be easier to keep track of upcoming testing events (.ics).
Our next testday is scheduled for this Friday, August 25th, where our focus will be on kicking the tires of some Firefox 2.0b2 candidates. Come join us in IRC, or test with Litmus at your leisure.
Zach Lipton returns to the Mozilla QA team as a summer intern. He’ll be helping me out with some of the outstanding Litmus functionality (about which I am particularly excited), as well as helping to develop new testcases in advance of Firefox 2.0. Welcome back!
Hopefully if you tried to use Litmus today, you didn’t find anything out of place, or if you were really paying attention, you noticed that a few annoying bugs had been fixed. No small feat when you consider how much of the database and back-end had to change to pave the way for a proper implementation of test runs, and these changes were all landed late last night. It’s always nice when your database migration scripts don’t require you to pull out the database backups.
Looking ahead, once test runs are implemented, casual testers will still likely not notice much difference in how Litmus testing will work, but it will bring Litmus the tool more in line with how the Mozilla QA team likes to manage testing internally, especially as it pertains to releases. We’re not quite ready for test runs yet, but this was a important step forward.
More to come soon!
As was foretold, Zach landed his authentication code last week. After some quick fix-ups and subsequent bake-time this week, I flipped the switch and made the changes live today.
Account creation occurs as part of the regular testing procedure, i.e. it’s an interim step after you’ve decided you want to “run tests.” If you’ve tested with Litmus before, you can upgrade your current testing “login” (that’s the email you supplied previously) to a full account. New testers can simply create new accounts.
If you’re having problems with the new authentication system, the best way to get it resolved is to join us in IRC (irc.mozilla.org, channel #qa). One of the operators there — probably me, coop — should be able to help you.
I’ve added a set of localization (l10n) tests for Firefox to Litmus. These are the same tests that we use internally for validating localized Firefox releases.
It’s quite possible that some of these testcases will need clarification. If that does turn out to be the case, please let me know by marking the testcase as unclear in Litmus or by commenting here. Thanks!
