QA/StaffMeetings/QA-Staff-04-02-2014

From MozillaWiki
Jump to: navigation, search

Mozilla QA Meeting April 2, 2014

# Every Weds @ 1:30p Pacific Time - Mozilla HQ, Warp Core 
#
# Vidyo:  https://v.mozilla.com/flex.html?roomdirect.html&key=nL4PESn1IaVh
# 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://irc.mozilla.org:6697/#qa

Actions From Last Week

Discussion Zone

QA Show and Tell

https://wiki.mozilla.org/QA/Show-and-Tell#Schedule

Desktop

  • There is a web API where the geo location can ask where am I? It figures out what AP's it can see and then queries a big database of that data and then sends it back to the client that this is your location.
  • Google owns the server.
  • Browser needs to get AP info from the platform, send that using JSON to the server, get the response back, and then parse the result.
  • If wifi is off, if the server doesn't have the right data, etc there are likely issues.
  • One day soon we will be supporting that server

https://github.com/mozilla/MozStumbler/releases

Device No GPS

AGPS

  • Devices have GPS chips and devices can get that data - but it's slow. 50bits per second.
  • Will take a few minutes to get a fix on your location.
  • You can assit the chip gps by using the AGPS technology - an umbrella of technologies.
  • It basically is a server that tells your device where the satellites are.
  • You can't point it at just anybody's server - the people that own these want $$$$ for that access.
  • OEMs usually set up AGPS systems for the carriers. Carriers often operate the AGPS service. But the Carrier AGPS service only effectively works iwthin that carriers network. (which is given by the towers)
  • Moving forward we will still see the devices that are misconfigured.
    • Two things to help:
      • Patches that will toggle logging gps to the console - should land on 2.0 and 1.4, then when we have a person complaining about it we can get logs from them and then understand what is going on because we can't get info off the chip so this debugging will help us a bit to understand what is happening.
      • Use our server as a proxy (with cellular and wifi location information) which will give you a rough fix on location so you can do some lookup with a near proximity
      • The tarako chips and OEM have no GPS relationships so that device may never have support.
    • there is scanning in the low levels of the code, but we are not going to see it in our application layer

The Tarako approach will be to scan wifi in target locations and hope that gets you in a rough locale Architecture on B2G

  • QC changes our stack when we "ship" our code. One of the things they change is our GPS code. So we don't know what is in there.
  • Our stack is in Gaia, Gecko, and Gonk.

Bug Diagnosis

  • We cannot diagnose or fix anything that replaced our code
  • If it is something tha touches our server then we want to care about it - first ship of that will be desktop and tarako
  • Bad accuracy, long time to fix - then nothing we can do on our size.

Better Testing

  • Ensure the prompting works as well and ensuring tha tyou get what you expect back from it and whether it changes over time.

Desktop there is a preference that can be set which will be a way to dump long - but not for users (pii concerns). Desktop there is an API key - need to ensure that it is sent and is correct or else it won't work.

Milestones and Calls for Action

Achievements

Upcoming

Internal Goals

Community

Contributor Welcome

These are new contributors, if you see them around, say hello

  • maja_zf, nmckenz, Dwarfplanet9, ankit.spaceo, Pankaj,

Contributor Honor Roll

For those that went above and beyond this week, we salute you here.

Updates

How To Find Us

Upcoming Events/Conferences

  • Community Leadership Summit (OSCON) - July 18-19, 2014
  • [henrik] Mozilla Hacking Day in Berlin on April 26th - I will show automation for QA and mentor people

Travel / PTO

  • [dclarke] PTO 04/1 - 04/12
  • [kthiessen] Services workweek in MV, 31 Mar - 4 Apr.
  • [geo] FxOS perf workweek Mar 31 - Apr 4
  • [mbrandt] PTO 04/08
  • [ctalbert] PTO April 12 - 27

Detailed Updates

Below follows detailed updates on what each team is working on and toward. The leads highlighted in each section are the people you want to find if you're interested in helping out.

Desktop (Juanb)

Mobile (Tchung)

  • Firefox for Android (Kbrosnan/AaronMT)
    • Delivered Firefox 29 beta 4
    • webapps landed, update issues
    • fxAccounts looks good
    • firming up Q2 goals
    • Stability (kbrosnan)
      • Looking into increased crash rate in beta
        • seems to be due to h264 crashes
  • B2G (Geo/jhammink)
    • Burirun 1.4-2: Wrapped up!
    • Tarakorun and Tarako Smoketests (builds available on PVT as of today, see notes below)
    • 1.3T Tarako Triage
    • 2nd Test Run for 1.4 Completed
    • 1.3T focus on testrun and bugwork, device dependent; builds are done
    • QA schedule is posted on google calendar <john to provide link>
    • performance workweek in taipei this week (Geo)
    • flame devices to arrive mid april
    • Open C 1.3 smoketests last week - ended by today
    • Biggest challenge - still need Flame builds (see bug 978888)
    • Pain point in bug 988979 causing SIM to not be recognized upon reboot
    • Stability (nhirata)
    • Devices (nhirata)
      • recommend getting off inaris ( bug 970403 )
      • Flame build : patches landed ( bug 978888 ); we should be getting them soon
      • no word on Sora, pinged TAM to see if we're going to get updates for them on teleweb
      • Open C : new base build (eng) as of today; have not tested; see intranet in order to get a build if you need it.
        • Taipei team has asked us to use the flame gecko/gaia on top of the Open C base build
      • tarako builds are now available on pvtbuilds: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g28_v1_3t-tarako/
        • you will need linux in order to flash the device as well as a u-boot fix. Read intranet for more info on the setup and fix.
        • you will want to download the tarako.zip as we flash via imgs. system.img contains gonk, gecko, gaia levels.
    • Misc: (nhirata)

Services (Edwong)

  • FxA
    • Working on mozmill automation
    • Load testing and capacity planning
    • adding marionette-js tests to improve dev efficiency
  • Sync
    • Load testing - investigating bugs
    • investigating battery life issues on Fennec
  • Loop
    • Initial planning.
  • WMF/FMD - targetting 1.5
    • Peter will focus on server bits.

Web (Stephend)

Firefox Automation (Whimboo)

  • General
  • Projects
    • TPS
      • Good progress, only two failing tests are remaining (bug 981706)
      • TPS CI is running again and reports 26 pass / 2 fail (1 of those failures is actually a bug in Sync)
    • Mozmill
      • Lots of regressions (SSL, video) and sporadic crashes this week
      • Working with mmc on possible safe browsing tests for Mozmill
  • MozTrap (Camd)

Action Items

  • Kevin to set up a dribble for qa team week weeks mid june to july
  • All finialize goals for Q2

Template available at: https://etherpad.mozilla.org/qa-mtg-template

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/StaffMeetings/QA-Staff-04-02-2014&oldid=962226"