B2G/QA/Meetings/Automation/2015-03-05

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)

    • https://wiki.mozilla.org/B2G/QA/Automation/UI/Strategy - Q1 for each section under Plan
    • 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

March 5, 2015

Attendees

  • Geo, Johan, Martijn, Peter, Oliver, John, Parul, Naoki

Previous Action Items

  • [Geo] Create "team" user to follow email
    • [Geo] deliver bug template including these instructions
      • In progress

Status Highlights / Agenda

  • [PBylenga] New issue seen after running automation locally, No-Jun to write, seems a recent regression, not 100%
  • [geo] Lots of failures on yesterday's automation report. Please help triage.
  • [oliverthor] Random plivo calls being encountered locally when not performing automation
    • [jlorenzo] Are they happening on the devices in the lab? If you have some details about the time it happened, I can dig in the logs in the Plivo website
      • It was on my personal device; I had shared my testvars file with no-jun to help him debug his credentials so I was curious if he was somehow using mine. He told me had swapped out those numbers.
    • [jlorenzo] I checked the logs and the debug logs, I can't have the IP which has initiated the call. We might be able to call the support
      • How about the time, or anything else that seemed to happen in the same session? Might help fingerprint.
  • [geo] Please xfail/disable tests early

This Week - Decisions & Action Items

  • [Geo] to figure out QA moderation, room call in number, etc.
  • [Geo] Create "team" user to follow email
    • [Geo] deliver bug template including these instructions
      • Carry over
  • [Geo] send out xfail examples