B2G/QA/Meetings/Automation/2015-01-22

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

Overview

This is a weekly meetup to discuss all things regarding B2G automation and Quality. Please use wiki style.

Q1 2015 Goals

2.2 - (OS QA (in Taiwan)

    • Support the stability of 2.2 branch with focused test runs, qawanted, bug triage, and daily smoke tests (manual and automation)
    • Support new feature testing
    • Manage the release out the door until CC date, and hand off to Devices QA team into Q2.

3.0 - (OS QA (in US/EU)

    • Automation goals:
      • Re-evaluate the smoke tests on v3 that will be needed for automation in javascript
      • Focus on getting existing Gij tests running against the lab of devices
      • Creating a set of best practices on creating JS gaia-UI automation tests
      • Focus on getting smoke tests running against the lab of devices (could be a combination of Gij, python, or JS tests).
    • Support the stability of master with focused test runs, qawanted, bug triage, and daily smoke tests (manual and automation)
    • Support lightweight dogfooding program off of nightly
    • Develop feature testplans when features are concrete

Attendees

Previous Action Items

[Tony] request v18D-1 with adb enabled access from T2M

[Tony] MarionetteJS bugs from James

    • Geo to follow up.

Status Highlights

  • [Bebe] Bug 1121374 - Devices crash during test runs and can no longer be found via ADB
    • We are investigating the issue but can't reproduce the bug locally
    • Bug 1122119 - [System] Device randomly white-screens, becomes unresponsive, and spams computer (if connected) with 6 device folders

==

  • [Peter] Discuss implementing Developer Status for stability for 3.0 (Master)
  • White screen bug
    • Currently unknown cause, many developers contributing to 1122119. Bhavana to follow up with mwu(?)
  • [Bebe] When should we update to v18D-1
    • Geo to follow up with releng to know what we're bundling -- are we frankenbuilding?
      • (catlee should know)
    • Are the reports still valid w/ different base build?
    • Naoki: flash 18d+shallow instead of deep?
      • Manual should go to full runs for overlap if this is picked

This Week - Decisions & Action Items

  • [jlorenzo] Bug 1122119 - Leave a phone shallow flashed running on the clock the entire night and see if it crashes.
  • [Peter] Draft a proposal for Developer Status and present it to QA Owners initially