B2G/QA

From MozillaWiki
Jump to navigation Jump to search

Overview

B2G (Boot 2 Gecko) is a new and exciting web platform that Mozilla is developing on mobile devices. The project will focus on the following:

  • New web APIs: build prototype APIs for exposing device and OS capabilities to content (Telephony, SMS, Camera, USB, Bluetooth, NFC, etc.)
  • Privilege model: making sure that these new capabilities are safely exposed to pages and applications
  • Booting: prototype a low-level substrate for mobile devices (phones and tablets)
  • Applications: choose and port or build apps to prove out and prioritize the power of the system.


Team Details

The B2G QA team is committed to qualifying the full spectrum of testing from backend (Gecko) to Frontend (Gaia). Test coverage will include a range of manual execution steps, automated test coverage, proper documentation, and community involvement projects.

Join us

If you want to help on the B2G project, it's very easy to start.

Subscribe to our QA team mailing list and send us an e-mail presenting yourself and telling us what kind of tasks you would like to do.

Also you can find us on irc.mozilla.org on #b2g

Team Members and Assignments

Name Contact Availability Project Assignments
Geo Mealer gmealer@mozilla.com MoCo Employee (full time) Testing b2g, api automation, strategy
John Hammink jhammink@mozilla.com MoCo Employee (full time) Testing Gaia, frontend automation, building, and documentations
Naoki Hirata nhirata@mozilla.com MoCo Employee (full time) Testing Gaia, frontend automation, stability
Martijn Wargers mwargers@mozilla.com MoCo Employee (full time) Testing B2G, webapis, automation, Geolocation
David Clarke dclarke@mozilla.com MoCo Employee (full time) Testing B2G, webapis, automation, Video
Jason Smith jsmith@mozilla.com MoCo Employee (full time) Testing Gaia, marketplace, Apps
Matt Brandt mbrandt@mozilla.com Part time Testing, automation, strategy
John Shih jshih@mozilla.com QA Intern Testing Gaia, B2G, testplans
Tony Chung tchung@mozilla.com MoCo Employee (full time) QA Team Manager
Santiago Hollmann santiago@mozilla-hispano.org Part time Testing Gaia, frontend automation
Add your name here! email time allotted duties

Communication channels

  • Mailing list: This is our main communication channel. Here we share tasks, thoughts, problems, etc. On this list we organize the team. https://lists.mozilla.org/listinfo/qa-b2g
  • IRC (irc.mozilla.org): You can find us on #b2g

Bug Triage

B2G does a platform and frontend bug triage each day with Engineering, QA, and PMs. The times and location is captured in the B2G Meetings page.

Mozilla QA rotation schedule

Gaia Triage
  • M - Naoki Hirata
  • T - John Hammink
  • W - Naoki Hirata
  • Th - John Hammink
  • F - Marcia Knous
Gecko Triage
  • M - Jason Smith
  • T - Geo Mealer
  • W - David Clarke, Martijn Wargers
  • Th - Jason Smith, Martijn Wargers
  • F - Geo Mealer

This list just guarantees at least one represntative to the daily triage meetings. Anyone can attend. I recommend as often as you can because there is invaluable communication, collaboration, and decision-making that creates a equal voice.

Projects

This section should contain a list to the active current team project page. The section will be included as part of the top level QA organization page.

Project Description QA Owner
Gaia Test Plan The testplan highlighting coverage for Gaia. Tony/John
WebAPI Test Plan The test plan for B2G-related Web APIs Geo
Installation Documents Documentation on setting up, installing, and getting started with B2G John H
Gaia Automation Gaia Automation John S


Environments

<this section to include the environments needed to run and setup B2G>

  • Weekly Builds - documentation on how daily and weekly builds will be generated. Direct build links will only be available to internal B2G team, but a manifest file supporting build information will be made public so others can build on their own environment.

Resources

Bug Queries

Meetings

Team Goals

Community Contribution

Anyone can participate. There are several ways in which YOU can participate:

  • Install the QEmulator
  • File bugs
  • Triage bugs (confirm existing bugs and assign them to the right buckets)
  • Help test new features
  • Write test cases
  • Plan new features testing
  • Help others who want to get involved.