Mobile/Testing/11 18 15

From MozillaWiki
Jump to: navigation, search

Previous Action Items

Status reports

Dev team

Rel Eng

  • Gave a talk at USENIX release engineering summit in Washington, DC last Friday on scaling our Android testing on emulators as well as a lightning talk on making our buildfarm more resilient to failure. Slides are here http://www.slideshare.net/k2moir/scaling-mobile-testing-on-aws-emulators-all-the-way-down. I asked if any people in the audience run Android tests on commit on a few hands went up but there wasn't anyone there who tested at the scale that we did. There was a representative there from Google but they didn't talk about scaling Android but rather deploying machine learning models for AdSense and other products. Lukas Blakk from Pinterest (previous Mozilla releng and relman) gave a talk about their mobile release process and mentioned that they use https://xamarin.com/ for their mobile testing, they even write tests for them to improve coverage.

A Team

  • android-2-3-armv7-api9 Total failure rate: [1.2%]
    • last week 1.21%
    • total failure excluding retries 1.03%
  • android-4-3-armv7-api11 Total failure rate: [1.72%]
    • last week 1.58%
    • total failure excluding retries 1.09%

Data fetched for: 2015-11-11 11:08 — 2015-11-17 21:21

Autophone

  • tp4m/tsvgx saw a regression and corresponding improvement with the backout of bug 1210261. Over the last couple of weeks these tests have been running reliably and stable.
    • is nexus-7 the right hardware?
    • what level of coverage do we want before turning off the pandas?
  • [bc] debugging unit test runners in preparation for enabling mochitest-dom-media. Lots of twisty little passages but I found the lamp.

Perfherder

Round Table

Action Items