B2G/QA/2.2

< B2G‎ | QA
Revision as of 05:07, 26 November 2014 by Tchung (talk | contribs)

Team Breakdown

Here is a table indicating QA contacts by major areas for Firefox OS 2.2.

Area QA Contacts
Management Tony Chung, Brian Huang
Release Lead Tony Chung
Productivity Teri, Wen, Edward Chen, Tony Chung
Media No-Jun Park, Alison Shiue, Eric Chang
System Front End Marcia Knous, Parul Marthur, Hermes Cheng
Communications Eric Chang, Johan Lorenzo
Performance Geo Mealer
Networking/Connectivity Alison Shiue, Eric Chang
System Platform Gerry Chang
Multimedia Platform Edward Chen
Devices Alison Shiue, Naoki Hirata (Flame support)
Graphics No-Jun Park
Metrics Shing Lyu, Gerry Chang
Localization, RTL Delphine Lebedel
Stability Paul Yang, Walter Chan

Feature Complete

Release Signoff Status

Health:

Feature Complete Criteria
  • All feature landing exceptions must be resolved
    • No
  • Bugs with keyword late-l10n should be zero
    • No
  • Chipset vendor requirements or bugs needed to meet their FC date must be resolved
    • CAF FC for 2.2 not met
  • Completed one functional test run
    • No.
  • QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels its qualitatively ready -
    • No.
  • Smoketest Greenness - Latest length of time that we haven't had smoketest regressions needs to be greater than five days
    • No,
  • MTBF Test Run lasts for 30+ hours:
    • No.
  • Perfomance team sign-off to ensure we have met the FC ready criteria
  • No.
Additional QA notes
  • Branch and bug verifications since Oct 9th
    • Bugzilla Query:
Remaining QA items

Feature Landing

Release Signoff Status

Functional Signoff Status

Smoketest Status

Nominations

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Blockers

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Gaia UI Test Regressions Status

Nominations

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Blockers

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Test Coverage Status

Test Coverage Needed

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Test Coverage Completed

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Test Coverage Declined

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Verification Status

Overall Verification Summary

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Verification Needed

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Verification Complete

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Definitions

Health Notations

  • [ON TRACK] QA thinks the health is trending towards green, but signoff isn't complete yet
  • [AT RISK] QA thinks the health is trending towards yellow, but signoff isn't complete yet
  • [DONE] QA has signed off to indicate the health is green
  • [MISSED] QA has chosen to not sign off to indicate the health is red

FL Functional Team Criteria

The functional team FL health was determined against the following criteria:

  • MozTrap test coverage done?
  • All user stories verified to spec?
  • Smoketests green around your area?

The lowest health score out of each of the criteria above is used as the team's overall health status.

FC Functional Team Criteria

The functional team FC health is determined against the following criteria:

  • Have all features gone through a functional test run?
  • Did any risky feature areas get exploratory testing?
  • Were smoketests around your area green for 5+ days?
  • Did each outstanding FC signoff blocker get fixed?

The lowest health score out of each of the criteria above is used as the team's overall health status.