QA/StaffMeetings/QA-Staff-04-04-2012

From MozillaWiki
Jump to: navigation, search

« previous mtg | QA Staff Home | next mtg »

QA Staff Meeting Notes April 4, 2012

Meeting Details

 # Every Weds @ 1:30p Pacific Time - Mozilla HQ, Warp Core 
 #
 # Vidyo:  https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym
 # Phone:  +1 650 903 0800 or 650-215-1282 x92 Conf# 95312 (US/INTL)
 #         +1 800 707 2533 (pin 369) Conf# 95312 (US Toll Free)
 #         +1 416 848 3114 x92 Conf# 95312 (Canada)
 # IRC:    irc://irc.mozilla.org:6697/#qa

QA Org Items

  • New Hires & Interviews
    • Job Descriptions for Services QA have been posted to Mozilla careers and JobVite
  • Community Members Onboarding
    • John Hammick mentioned we have 4 contributors in Argentina actively working on Boot to Gecko!
    • New WebQA contributor Pengsu!
    • Wikipedia is asking about MozTrap
    • Mobile contributor: Ken Barbalace, helped with bug hunting and regression range. Mozqa tshirt is on the way.
  • Upcoming Events
  • PTOs
    • Friday is a public holiday in Canada and Europe
    • Juan is on PTO all week, back next week

QA Team Updates

Desktop Firefox

  • Firefox Desktop
    • Firefox 12.0b4 candidates available, trying to release by EOD-Thursday
    • Firefox 12 is the end-of-the-line for users running Windows XP SP1 and earlier; will have a billboard asking them to update their operating system. Being deployed using Add-on Hotfix, giving users 2 weeks notice (testing on Apr 16, live on Apr 17)
    • Java 6u30 and older is being blocklisted for security reasons, please keep that in mind as you are triaging support, mailing lists and bugzilla
  • Firefox ESR
    • Nothing new to report at this time
  • Firefox 3.6
    • EOL with Firefox 12's release; users will be offered update to Firefox 12 indefinitely (3.6 -> 12 -> latest). Not ESRing these users because of support requirements (ie. ESR is untested/unsupported for a general user population)
  • Crash Investigation

Browser Technologies (Tony)

  • Highlights
    • Goals planning
    • Fennec Native Beta will build off of Aurora branch, targeting April 26
    • Full client-side Selenium II automation has been handed off to WebQA for Q2
    • Active QA planning on Apps In the Cloud from web, apps, mobile, services, and desktop
    • B2G shipped Milestone 2.5 on Nexus S to 300+ attendants at JSConf
  • Fennec (Kevin/Aaron)
    • The initial release of Firefox mobile native will be on the 14 train
      • This will be a shortened cycle Aurora and Beta
    • Stability (nhirata)
      • the 1st, 2nd, 4th and 7th crashes seem to have been fixed. Need to wait for everyone to update and numbers die down.
  • Apps WebRT (David/Jason/Aaron)
    • What happened this week?
      • Lots of discussion on Q2 Goals for Apps here
      • Mobile web compatibility testing on-going here
      • App Quality Checklist on-going being built here
    • What's next?
      • Finalize Q2 Goals for Apps
      • Continue digging into mobile web compatibility problems on gecko
  • Sync (Tracy)
    • Fixes on Android continue to trickle in. Tab Sync (one way: from desktop to mobile) and form history are the latest features to land. Note: form history is pref'd off until the Fennec content provider performance improves. see bug 740218 - Fennec form history content provider insert is slow on Transformer Prime
    • A desktop client train rolled last week with some setup refactoring. Mostly just performance and stability work
  • Test pilot (tracy)
    • Currently testing an updated version of the UI study. 2012 UI heatmap study.
  • Sync Server (jbonacci/jrgm)
    • Initial testing of Sync 2.0, AITC 1.0, and TokenServer on local installs has completed.
    • Test Planning for the following:
      • AITC in Dev, Stage, Prod, including functional and load
      • TokenServer in Dev, Stage, Prod, including functional and load
    • Future projects
      • Notifications
      • Sync 2.0 API
  • BrowserID (jbonacci/jrgm)
    • Work has started on Train 24: Bug 740272 - QA and deploy BrowserID train-2012.03.28 to production
    • Services QA team will be splitting time across BID and the April AITC work
    • Full client-side Selenium II automation has been handed off to WebQA for Q2
  • Pancake (nhirata)
    • Origami theme landed last week
    • front end still needs some work before beta release
  • B2G (geo/jhammink)

WebQA (Stephen)

Community (Marcia)

  • Upcoming Events
    • MozCamp Latin America
      • Both of our proposed sessions have been accepted and are going forward - Mobile Testing Workshop and Crash Investigation
      • Juan and Marcia will spend time working with Gabriela 1:1 on some of the other testing topics she is interested in.
    • Mini QA-MozCamp in Italy
      • More discussion about this event at the QA Community meeting today. Need to decide whether there are enough topics for a two day event or whether the event needs to be scaled down.
  • Video Work
  • QMO.next (Raymond):
  • Misc.

QA Automation Service (Henrik, David)

General

  • All Q1 2012 goals have been accomplished!! Kudos to the whole team!

Project updates

On-Demand Test Framework (Geo)
Mozmill 2.0 Automation Scripts Update (Henrik)
  • Investigation has been finished. Coding can start hopefully by next week.
CI system for daily and l10n Firefox Builds (Henrik)
  • System is up and running on http://release3.qa.mtv1.mozilla.com:8080/
  • Reports are uploaded to http://mozmill-ci.blargon7.com/#/
  • We are testing daily builds:
    • mozilla-central, mozilla-aurora, mozilla-esr10, and mozilla-1.9.2
    • OS X 10.6, Ubuntu 32/64, Windows (2k, xp, vista, win 7 32/64)
  • We are testing l10n tinderbox builds:
    • mozilla-central, mozilla-aurora
    • OS X 10.6, Ubuntu 32, Windows (XP, 7 32)
  • Will move to a grid of machines by probably next week
Mozmill Dashboard Validation (DavidB)
  • Code has been checked in and deployed.
MemChaser extension
Open Positions (DavidB)
  • No update
Weekly Blog Posts
  • No update
MozTrap
  • 1.0 was shipped last week
  • We have a name: MozTrap
  • 1.0 Deployed to staging yesterday
  • new URL: https://moztrap.allizom.org/
  • Selenium tests are passing via Jenkins
  • Aakash put some guys from Wikipedia in touch with me on evaluating MozTrap. We're in talks over email.
  • Working on new features and bug fixes going forward

Roundtable/Discussion Items

  • What does Kilimanjaro mean to QA? [jsmith]
    • What stays? What changes?
    • How does it affect the organization as a whole?
    • How does it affect the QA-specific teams (e.g. desktop, web, mobile)?
  • How is Kilimanjaro being messaged to the community? [marcia]
  • Cross QA Team Collaboration Reflection [jsmith]
    • What are we doing well?
    • What are we not doing well?
    • What should change in Q2?
    • How do we address cross-functional feature ownership to promote team collaboration?
  • Windows 8 Tablets for Testing, Dogfooding, etc. Firefox on Win 8 Metro [jsmith]
    • Testing - Desktop & Mobile Need to Collaborate
    • Ownership under the new org
    • Dogfooding for the team as a whole
    • Other random items involving Win 8 Metro
  • Automation Services
    • Meeting attendance
    • Expectations
  • Status of Q2 Goals?

Notes, Takeaways and Action Items

Today

  • Notes
    • marcia will work to figure out how we keep Firefox shirts in stock for contributors
    • Cool dashboard to check out: http://wrla.ch/eideticker/dashboard/#/scrolling
      • Wonderful opportunity to use this for desktop, startup testing.
      • Think about ways to use in your own areas. Talk to Clint if you are interested in finding out more.
    • B2G dogfooding event coming in June
    • Q2 Goals due to Bob by the end of the week
    • Thanks to David, Geo and David and Henrik for helping us to get across the finish line
    • Kilimanjaro
      • Integration of a whole bunch of moving parts
      • More emphasis on looking at the integration points
      • Web as a platform
      • A lot more in test plans around the integrated workflows - User stories
      • Really smart about how we put probes in place.
      • How do we look at logs on servers
      • This will cause QA to behave as a single team.
      • Regular triage of Kilimanjaro bugs
    • Cross QA Team Collaboration Reflection - Come prepared at next staff to do this

Last Meeting

  • Action Items
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/StaffMeetings/QA-Staff-04-04-2012&oldid=416880"