In the beginning of the Mobile Firefox (Fennec) project, none of our existing tests would run on either the emulators or the devices. As one developer put it, “It’s like we’re driving down the road at midnight with no headlights”. Because much of the Fennec code reuses the same core platform technology that Firefox is based on, it made sense to move our existing test frameworks to the mobile OS’s.
That was a deceptively simple idea, but as we got started, we found that it is actually anything but simple. We hit every hurdle you could imagine: from the fact that our test system was too tightly coupled with our build system, to the memory and space issues you’d expect, to color palates, to reliability.
We will talk about all the various challenges we faced in stuffing these test frameworks into the tiny footprint of a phone. After confronting different instances of this problem for Maemo, Windows Mobile, and Symbian; we have learned a set of lessons and best practices that could apply to any project that is trying to “go mobile”.
Clint started with Mozilla as a volunteer by organizing a QA team for the Calendar project. From there, he became a calendar module owner, and then was hired by Mozilla to work on test development. He is currently the Test Development Lead for the Mozilla QA team.
Joel has been a technical lead for the Mozilla effort to create the automation infrastructure on our mobile platforms.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the OSCON Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the OSCON newsletter (login required)
View a complete list of OSCON contacts