Mobile/Community

As the mobile project nears a release, we need to start spreading the word and leveraging the community (either as feedback, testing, development, or evangalism).

Testing

• Testing involved:
  • Device compatibility and installation
  • Website compatibility and accuracy
  • Crash reporting and bug filing
  • General feedback (it takes too long, I NEED this feature)
  • Running a set of pre defined test cases to verify detailed features
  • Verifying localized builds are functional and accurate

• One of the easiest methods to get active involvement from the early adopters and community members is to provide a QAC (QA Companion) style add-on which would (with the users permission):
  • Collect information about the device and network
  • Allow for running litmus tests
  • Allow for easy bug filing including basic device info and screenshot with a single click

The mobile QAC is scheduled for development the first half of Q3 2009, so we will be able to leverage this in the near future!

• Feedback channel (SUMO, crashreporter)? We need a real feedback channel and place for people to read FAQ's, collaborate and ask questions. Also with the high risk of crashing, we need some kind of crash reporting system.

Will discuss our approach for this in Q3 2009 and have a plan in place if not already in the works.

What We Have

• We have created a mailinglist for anybody interested in mobile testing: mobiletesters@mozilla.org

• We have setup an account with DeviceAnywhere to leverage up to 62 different devices. Options to utilize this service for more devices and coverage.

• QA team has a few extra devices (HTC Touch Pro, Samsung Omnia) as well as different cellular data plans.

• WebDev is working on the fennec webdev project. QA is involved to test that as well as compatibility with devices and fennec.

• Fennec [Web Compatibility testday] scheduled June 26th. This is advertised on QMO, Facebook, and the QA mailing lists. We plan to do more of these in the future.

• Test Development [projects] for mobile outlined.

• 2 community members contributing weekly, and 2 others who have contributed and have expressed interest in further contributions. All of these are towards test development.

• A one new hire in TestDev who will provide some extra help to get Mobile QAC started. Still working with three other volunteers on the QAC project as well.

Going Forward

• Develop mobile QAC in Q3/2009
• Solidify plans and next steps in Q3/2009 for crashreporter, feedback channels
• Continue development of automation and unittests
• Utilize deviceanywhere to smoketest devices and verify bugs found in the field
• Take advantage of testdays and mailing lists to promote new features and areas to focus on