From MozillaWiki
< B2G‎ | QA‎ | Meetings
Jump to: navigation, search


Status Highlights

2.1 Release Update


  • 2.1 Health Dashboard - https://wiki.mozilla.org/B2G/QA/2.1
  • Each team should identify QA call outs & any blockers on a per team basis
  • Provide a FC health assessment 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?

Features (Organized by Functional Team)


  • Health: Green
    • 7 blockers, 3 of them has target milestone in S5, 2 of them are assigned, 2 of them are need to be confirmed.
    • http://mzl.la/1mcHbYM


  • Health Callout: Green
  • [njpark] Discussing acceptable performance number for media apps. Seems that there is a difference between the logcat and what datazilla reports
  • [njpark] Turns out extra processes are running on device after FTU: https://bugzilla.mozilla.org/show_bug.cgi?id=1068826 to track issue

Multimedia Platform

  • Note - need an update from Edward


  • Health: Green (Tony)
    • bugs filed, but nothing that is concerning that would miss FC
  • 2.1+ Bugs:
    • 1068116 [email] POP3 accounts cannot view attachments
    • 1030798 [Calendar] Month view: day header and event time are not localized when changing languages
    • 1052960 [Calendar] Day View: update it to use same logic as the 5-day week view
    • Bug 1067270 - [Calendar] Add Google calendar via OAUTH always show something wrong.
    • 1018833 Calendar sync duplicates events

Systems Front End

Status: Yellow

Systems Platform

Status: Green


  • Note - need an update from Eric, Gerry, Alison
  • Health: RIL: Green
    • 1 blocker


  • Note - need an update from Alison
  • Bluetooth PTS
    • Bluedroid + KK - 15 fail cases, blockers, RD are working on them.
    • BlueZ - 1 fail case



  • [tchung] discuss team triages, and when/where they are held
    • https://wiki.mozilla.org/FirefoxOS/functionalteams <-- has triage info, may be out of date.
      • SFE ; sometimes in standups/sprint planning (tues/thurs 8:30am PST)
        • Bi Weekly Triages Thursdays at 10:30 AM PST
      • productivity: sprint planning meetings (tues 5pm PST)
      • Media: wednedays (3:30pm PST)
      • Graphics: none. they do this on their own time
      • COMMS - triage (THU, 15:00 GMT+8)
      • RIL - triage (WED, 11:00 GMT+8)
      • Sys Platform - ??
      • FMD/FXA (THURS 11:00 PST)
      • NFC - ??
  • [geo] discuss performance numbers again and what to look for
    • Will be centrally conducting a comparison test between 2.0 and 2.1 w/ high number of repetitions, will give us something we can compare cleanly for acceptance.
    • Will publish test results and inform the team (and org) of issues w/ individual apps
    • In the meantime, you can look at Datazilla (turn off all checkboxes except apps you care about) and use the graph trends to identify regressions in launch time over 2.1 dev, and whether 2.1 looks worse than 2.0. Start those conversations in your team.
    • For things other than launch latency, we do not have automation and will not in any short order. Performance issues other than that need to be handled case-by-case within teams.
    • Perceived performance is the most important thing, so file bugs on anything that seems sluggish or not responsive. *If you notice the performance, it's probably not good.*
    • Do side-by-side videos with camera to show the issue in preference to trying to specifically time things. Timings require a lot of repetition to be accurate, whereas major issues usually show up on video. All we need to illustrate is there's an issue.
  • [jsmith] SIM Customizations QA Ownership
  • [jsmith] Majority of jsmith's bug queries are here - https://wiki.mozilla.org/B2G/QA/Weekly_Bug_Review
  • [jsmith] Process changes with KK parity being achieved
  • [tchung] thank you Jason! Keep in touch!

This Week - Decisions & Action Items

  • [jsmith] Email smoketest process changes to KK
  • [brhuang] Find out if there's capacity to handle SIM customizations QA?

This Week Notes