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


Status Highlights

  • Bug 1104338 - [b2g] we need root access on the b2g builds ( 2.2 )
    • Q4 Goals B2G (Draft)

2.1 Overall blockers

noms = http://mzl.la/1ATgdGM blockers = http://mzl.la/1l1nmh4

2.2 Release Update

Features (Organized by Functional Team)

Overall Concerns

Remaining Tasks

Text Selection work

  • Shing Lyu
  • Health Status:
  • Details: sent out guidelines to follow


  • Contacts
    • Tester: Johan Lorenzo
    • Health Status: Green
    • Details: 1 blocker (bug 1094966), the Facebook redirection changed on the Facebook side.
  • Dialer
    • Tester: Johan Lorenzo
    • Health Status: Green
    • Details: No blocker
  • Cost control (SmartData)
    • Tester: Johan Lorenzo
    • Health Status: Green
    • Details: No blocker
  • SMS
    • Tester: Eric
    • Health Status: Green
    • Details: No blocker


Multimedia Platform

  • Tester: Edward
  • Health Status:
  • Details:No new features


  • Tester: Edward, Teri
  • Health Status: Green
  • Details:No blockers

Systems Front End

  • Tester: marcia/pragmatic
  • Health Status: Green
  • Details:
    • 2.1 Blocker:
    • Features
      • https://bugzil.la/1067435 (app-grouping) [meta] Home-screen grouping - has landed, and App Grouping bugs can start being verified. Test cases are in progress.

Systems Platform

Metrics Testing =

  • Tester: Shing Lyu
  • Health Status: Green
  • Details: No blocker


  • Tester: eric
  • Health Status: Yellow
  • Details: unable to call out emergency from sim2 1089566
  • NFC Tester: Alison
  • Health Status: Green
  • Details: No blocker


  • Bluetooth Tester: Alison
  • Health Status: Green
  • Details: no blockers, need update on features


2.1 Smoketests

2.2 Smoketests


  • Tester: delphine
  • Health Status:
  • Details:


  • Tester: delphine
  • Health Status:
  • Details:


  • Tester:
  • Health Status:
  • Details:

MTBF Stability

  • Tester:
  • Health Status:
  • Details:



  • Portland Work Week: FxOS CoreOS sessions https://docs.google.com/a/mozilla.com/spreadsheets/d/1eP0CXx1OM5TxjkpWGGOZzS6udXFILM1nlK4GihJpBY0/edit#gid=0
    • see more relevant sessions at the bottom of this etherpad
  • [Shing] For Text Selection, please read https://etherpad.mozilla.org/TextSelectionTest
    • Bugzilla: QA whiteboard [textselection], MozTrap: textselection tag
  • [jlorenzo] Portland: The Moztrap meeting and the RTL kickoff are at the same time (December 2nd, 3PM PST).
    • [delphine] Candice organized that RTL Kickoff meeting
  • [delphine] RTL bugs: QA whiteboard [rtl-impact], Moztrap tag: rtl
  • [Tchung] QA whiteboarding [2.2-features-qa+] for 2.2 features in this list: https://mozilla.aha.io/published/7e3fcb6703be666bf40f322ccafb7e30?page=2
    • [eric] does the link contain all the features from draft spreadsheet 1? they have the same info?
  • [marcia] Please make sure Window Management bugs are not tagged with [systemsfe] in the Status Whiteboard. They are now under System Platform according to Candice. Also please note: If they are sysfe, please make sure the whiteboard tag [systemsfe] is used. We track our blockers here: https://wiki.mozilla.org/FirefoxOS/systemsfe/releasetracking
  • [Al Tsai, Shing] MozTrap Tool and Enhancements session at Portland Work Week
  • [Geo] Please nominate tests from your functional areas for Gaia regression testing automation.
    • Picking appropriate tests:
      • Prefer features that have settled and aren't changing currently, at least very quickly.
      • Prefer tests that are very repeatable, and happen the same way every time.
      • Prefer tests that have very clear and unambiguous success criteria.
      • Prefer tests without many dependencies on complex test data or external servers
      • Prefer tests that are already being run in our manual regression test runs, so we can lessen that effort.
      • That said, if nothing you need fits those criteria, nominate what you do need most and we can consider.
    • Filing an automation request:
      • File a bug in Firefox OS | Gaia::UI Tests saying "Automate test for [...]"
      • If test is in MozTrap, point at the MozTrap test case. Not much more is needed.
      • If test isn't in MozTrap, you can describe what you want in the bug. You do not need to define the test in MozTrap at this time. The condition that makes the test successful should be spelled out explicitly, the rest can be fairly general as long as it's reasonably obvious.
        • Ex: "Automate sanity test for status bar default icons," where description is "Immediately after a restart, the following icons should appear above the home screen...[list of icons]"
      • Worst case, we'll needinfo you for clarification, so don't get hung up on the description.
    • Tagging for nomination:
      • Please add [fxosqa-auto-backlog?] to the QA Whiteboard to get it into our triage.

This Week - Decisions & Action Items

  • [Peter, Kevin] make sure Qanalysts continues to own 2.1 regression , qawanted, smoketest work for next week

Relevant sessions for FirefoxOS QA at Portland Work Week

Location: Marriot Waterfront Ballroom D Tuesday, 12/2

  • 2-3pm: QA: Strategy and Goals meeting
    • Summary: This session will give an overview of the QA strategy for 2015. Please come to discuss and comment on what the roles and expectations will be for the OS and Devices QA team
    • Audience: drivers, QA
  • 3-4pm: QA: MozTrap Tool and Enhancements

Wednesday, 12/3

  • 11-12am: Gonk team: Power Tool and Auto Power Test by Jon Hylands/Danny Liang
  • 1-2pm: QA: Device automation strategy
    • Summary: This session will discuss the automation strategy in more details for FxOS testing going forward. It will also include framework and harness discussions, and how we can work with A-team to implement more test coverage.
    • Audience: QA, A-team
  • 3-4pm: QA: Reference phone Lab setup and testing (+A-team)
    • Summary: discussion on how we manage our flames, what base images we tests beforehand, and how we are designing and setting it up.
    • Audience: QA, A-team, Lab folks, Stephend
  • 3-5pm: Arabic Bug Bash
    • Summary: please bring your Flames and help with doing some BIDI (RTL) testing on FxOS
    • Audience: QA, Bidi folks, UX
  • 2-3pm: QA: MTBF improvements
  • Summary: discuss the MTBF stability strategy, how we define it today, and what we need to define and scale tomorrow.
  • Audience: MTBF QA, A-team, rwood, jlal

Thursday, 12/4

  • 3-4pm: QA WW Session: Defining Bug Verifications strategy
    • Summary: discussion on how we manage our flames, what base images we tests beforehand, and how we are designing and setting it up.
    • Audience: QA, A-team, Lab folks, Stephend