From MozillaWiki
Jump to: navigation, search

February 27, 2013

  1. Every Weds @ 1:30p Pacific Time - Mozilla HQ, Warp Core
# Vidyo:
# Phone:  +1 650 903 0800 or 650-215-1282 x92 Conf# 9245 (US/INTL)
#* *  +1 800 707 2533 (pin 369) Conf# 9245 (US Toll Free)
#* *  +1 416 848 3114 x92 Conf# 9245 (Canada)
# IRC:* irc://

QA Org Items

  • New Hires & Interviews
  • Welcome Edwin Wong! Services QA Mgr.
  • Upcoming Events/Conferences
  • SFHTML5 Conference on April 25th (jammink)
  • Notices

Travel / PTO

  • Tony & Marcia @ MWC this week (2/25-3/1)
  • Tony, Kevin, Aaron @ London mobile team week (3/4-3/8)
  • mbrandt @ Posse Roundup until next week (2/22-3/1)
  • mwobensmith @ Vancouver - BSides/CanSecWest 3/4-3/8

QA Team Updates

Desktop (Juan)

  • ESR (ashughes)
  • Stability (marcia)
  • Automation (ashughes)
  • Sync Client (Tracy)
  • WebRTC (jsmith)
  • MWC testing last week
  • Some getUserMedia signoff testing last week
  • Working on finishing off signoff testing for getUserMedia
  • Working on revised formal test plan for Peer Connections and Data Channels
  • Working on test app to better understand and test Peer Connection and Data Channel APIs
  • Security (mwobensmith)
  • Reviews/meetings around IDNs, CSP, cursor lock
  • Community

Mobile (Tony)

  • Issues
  • B2G (Geo/jhammink)
  • 1.0.1. testrun started but we have some issues:
  • previous testrun borked
  • Started with incorrect build Non-Vendor RIL and manifest not communicated down when the others went out
  • no easy way to reset testrun results from borked run
  • no clear way to create new testrun and carry over latest version cases - I had Al Tsai help with this for previous testrun but now he's out - and I do not know the steps. It's unintuitive.
  • I need help resolving this situation. For now we'll just rerun the existing testrun from the top, resetting the results as we go but I feel this is a less-than ideal solution.
  • Currently I'm having Qanalysts go back and reset their results manually in the testrun but the results are a mess
  • There was a delay in starting regression testrun for 1.0.1. - apparently we need to start testing with vendor RIL - actual nightly build has Moz RIL
  • Contractors/MozTesters have been working with
  • Regression Range Wanted bugs
  • QA Wanted bugs
  • TEF+ fixes:
  • Things are running a little slow because two of our main people are out at MWC
  • 1.1.0 - had UC review with P Dojanjski on friday; we'll most likely kick of testcase writing for 1.1.0 features by Wednesday this week
  • Stability (nhirata)
  • bug 844918 - crash in android::OMXCodec::signalBufferReturned
  • top crash
  • Second top crash is windows, and third, we don't have symbols for keon
  • Performance testing
  • Apps (Jason)
  • MWC testing last week
  • Misc apps bug verifications and qawanted testing
  • Focusing this week on web activities and system messages testing with apps
  • Also focusing on preinstalled app testing
  • Install/Update Gecko Automation Potential Blocker -
  • Community Members Onboarding

Services (jrgm)

Web (Stephen)

  • Affiliates
  • No updates
  • Engagement Projects
  • Firefox Flicks went out, subsequent releases for L10N work, bug fixes etc. on Thursday 2/29
  • MWC went out on Sunday 2/24
  • Firefox Marketplace
  • NO release this week because of MWC
  • Payments is still under test
  • Community Members Onboarding

Community (Marcia)

  • Projects
  • Upcoming Events
  • Video Work
  • Community Members Onboarding

Automation Development (Henrik, Dave)

  • General
  • We do no longer need the Mac Pro machines (qa-set, qa-horus). Does QA have needs for them?
  • Projects
  • Mozmill
  • With the latest release of Mozmill 1.5.21 we are green since Friday except for some very rare failures. Huge thanks also goes to the Softvision desktop automation team who helped us a lot to get down the number of failed and skipped tests. We are now ready to fully start with new tests - please tell us what you want to have automated!
  • Mozmill-CI
  • We stopped running ESR10 builds and shutdown Windows 2000 machines!
  • We will soon only run endurance tests for en-US builds to be prepared for testing more localized builds of Firefox
  • Mac minis for 10.6 and 10.7 will be shipped soon by IT - once setup we can kill the old CI
  • WebRTC
  • Henrik works on the refactoring of the PeerConnection test framework
  • B2G
  • Released gaiatest 0.8 with fixed support for B2G desktop client builds
  • Released b2gpopulate 0.5 with support for messages and improved contacts support
  • Released b2gperf 0.2 with several bugfixes and support for wifi networks
  • Fixed a long standing issue with Jenkins nodes for Gaia testing
  • New blog post: [Running Firefox OS UI Tests Without a Device]
  • Softvision have started working on Gaia UI tests
  • MozTrap (Cameron)
  • Community Members Onboarding
  • shouvik (firefox os)
  • bugcoder c3po (mozmill)
  • jgulbronson (mozmill-env)

Basecamp Roundtable/Discussion Items

  • [jsmith] B2G QA Bug Management - Up for Review, Feedback Appreciated -
  • [jsmith] leo triage - What is QA's perspective on what quality bar we should be advocating?
  • [jammink] need clear documentation on our work processes linked no fewer than 48 hours before we head out
  • RIL vs non-RIL and releng dependencies
  • Daily Smoketest depenencies

Other Roundtable/Discussion Items

Template for this document is here: