B2G/QA/2.5
Contents
- 1 Team Breakdown
- 2 Code Complete
- 3 Feature Complete
- 4 Feature Landing
- 5 Definitions
Team Breakdown
Testing
- V2.5 Contact window
- Overall : Naoki Hirata
- MGSEI related: William Hsu
- QAnalyst : Peter Bylenga / Kevin Tucker
- Automation: Johan Lorenzo
- Smoketest
- Daily by QAnalyst + MGSEI
- Make sure not breaking anything on flame-kk.
- Make sure working okay on L device.
- Daily report:
- Smoketest Automation
- Daily by
- Daily by
- Make sure not breaking anything on Flame-kk.
- Make sure working okay on L device.
- Daily report:
- gaia ui test -
- Automation new case creation & QA Ownership
- Feature, bug, functional owners will help on this.
- Full run
- Starting from FL by MGSEI, targeting twice in 6 weeks
- Also help to report invalid test cases.
- Mozilla will fix invalid test cases after that.
- Bugzilla related
- Marigold & Qanalyst will help with qawanted, verifyme & other tags.
- MTBF
- MTBF: Paul Yang
- Performance
- Overall QA Team
- gwagner is the dev manager
- Exploratory
- Will limit the scope of testing.
- By MGSEI + QAnalyst
- Usability testing
V2.5 QA Owners
Here is a table indicating QA contacts by major areas for Firefox OS V2.5
Feature by Components
Feature tracking by components
Feature Area Owners
| Area | QA Contacts |
| Management | Al Tsai, Pallavi Yaramada |
| Release Lead | Naoki Hirata |
| Productivity | Teri Wen, John Dolrus |
| Media | Alison Shiue, No Jun Park |
| System Front End | Naoki Hirata, Alison Shiue |
| Communications | Johan Lorenzo |
| Performance | All QA Members for their areas : see [[1]] |
| Networking/Connectivity | Alison Shiue |
| System Platform | Gerry Chang, Naoki Hirata |
| Multimedia Platform | No Jun Park |
| Devices | Askeing Yen |
| Bluetooth | Teri Wen |
| Metrics | Shing Lyu, Gerry Chang |
| Stability | Paul Yang, Walter Chan |
Reports & Update
Code Complete
Release Signoff Status
Feature Complete
Release Signoff Status
Health:
FC
- All feature landing exceptions must be resolved
- feature-b2g:
- blocking-b2g:
- Bugs with keyword late-l10n should be zero
- Yes,
- Chipset vendor requirements or bugs needed to meet their FC date must be resolved
- CAF FC for 2.5
- Completed one functional test run
- Yes, 2 runs.
- QA defines 2 areas of "functional areas" for exploratory testing and lead will send a "signoff" note when he feels its qualitatively ready -
- Yes.
- Smoketest Greenness - Latest length of time that we haven't had smoketest regressions needs to be greater than five days
- No, OTA issue is not yet resolved.
- MTBF Test Run lasts for 30+ hours:
- Yes.
- NEXUS-5-L 5.1 PVT build MTBF 38.5 hrs & counting.
- FLAME-KK 4.4 PVT build MTBF 34.42 hrs.
- blocking_b2g = 2.5+
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
- blocking_b2g = 2.5?
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Feature Landing
Release Signoff Status
Functional Signoff Status
Smoketest Status
Nominations
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Blockers
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Gaia UI Test Regressions Status
Nominations
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Blockers
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Test Coverage Completed
Everything with [2.5-feature-qa+] in QA Whiteboard
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Verification Status
Overall Verification Summary
Verification Needed
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Verification Complete
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
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
FLR Functional Team Criteria
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.
