B2G/QA: Difference between revisions

From MozillaWiki
< B2G
Jump to navigation Jump to search
Line 97: Line 97:
= Projects =
= Projects =


== Gaia QA ==
== Gaia & Gecko End to End QA ==


=== Overview ===
=== Overview ===


This group primarily focuses on doing end to end testing of Gaia's functionality, including the apps pre-installed on the device, phone features, etc.
This group primarily focuses on doing end to end testing of end to end functionality through Gaia and Gecko, including the apps pre-installed on the device, phone features, etc.
 
=== References ===
 
==== Test Plans ====


=== Test Plans ===
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email Email Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email Email Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Browser Browser Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Browser Browser Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Crash Crash Reporting Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Crash Crash Reporting Test Plan]


<onlyinclude>
==== Email Templates ====
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.
 
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email_Templates Email Templates]
 
== Gecko Automation ==
 
=== Overview ===
 
This group primarily focuses on automation development at the gecko levels.
 
=== References ===


{| class="fullwidth-table"
* [[/WebAPI Test Plan|WebAPI Test Plan]]
| style="background:#EFEFEF; width:25%" | '''Project'''
| style="background:#EFEFEF; width:65%" | '''Description'''
| style="background:#EFEFEF; width 10%" | '''QA Owner'''
|- valign="top"
| [https://www.pivotaltracker.com/projects/741071 B2G QA Process Backlog Tracker]
| Pivotal tracker for prioritizing todo/technical debt items. Add new items to [https://etherpad.mozilla.org/b2g-todo the collection etherpad].
| Geo
|-
| [[/Gaia_Test_Plan|Gaia Test Plan]]
| The testplan highlighting coverage for Gaia. 
| Tony/John
|-
| [[/WebAPI Test Plan|WebAPI Test Plan]]
| The test plan for B2G-related Web APIs
| Geo
|-
| [https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko Installation Documents]
| Documentation on setting up, installing, and getting started with B2G
| John H
|-
| [https://wiki.mozilla.org/B2G/QA/GaiaAutomation Gaia Automation]
| Gaia Automation
| John S
|}
</onlyinclude>


=Environments=
=Environments=

Revision as of 05:58, 22 April 2013

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 B2G 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 #appsqa

Team Members and Assignments

Name Contact Availability Project Assignments
Geo Mealer gmealer@mozilla.com MoCo Employee (full time) Gecko Automation Lead & Strategy
John Hammink jhammink@mozilla.com MoCo Employee (full time) Gaia QA Lead
Naoki Hirata nhirata@mozilla.com MoCo Employee (full time) Gaia Testing & Stability
Martijn Wargers mwargers@mozilla.com MoCo Employee (full time) Gecko Automation
David Clarke dclarke@mozilla.com MoCo Employee (full time) Gecko Automation
Jason Smith jsmith@mozilla.com MoCo Employee (full time) Gaia & Apps Testing
Tony Chung tchung@mozilla.com MoCo Employee (full time) QA Team Manager
Parul Mathur (pragmatic on IRC) Community Member Gaia Testing
Marcia Knous marcia@mozilla.com MoCo Employee (full time) Gaia Testing - Music, Video, and Misc Support
Al Tsai atsai@mozilla.com MoCo Employee (full time) Gaia Testing and Automation
Walter Chen wachen@mozilla.com MoCo Employee (full time) Gaia Testing and Automation

Bug Triage - QA Involvement

B2G does a daily triage to evaluate bugs for v1.1 that QA plans to be involved in on a daily basis. The below schedule shows who intends to show up to which triage on a weekly basis.

  • Monday 8am - David
  • Tuesday 4pm - Geo
  • Wednesday 8am - John
  • Thursday 4pm - Jason
  • Friday 8am - Tony, Tracy


This list just guarantees at least one representative 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

Gaia & Gecko End to End QA

Overview

This group primarily focuses on doing end to end testing of end to end functionality through Gaia and Gecko, including the apps pre-installed on the device, phone features, etc.

References

Test Plans

Email Templates

Gecko Automation

Overview

This group primarily focuses on automation development at the gecko levels.

References

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.
  • Flashing a Daily build. This requires mozilla access only to retrieve the builds. But the steps are the same for flashing on any device.

Resources

Bug Queries

Meetings

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.