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

previous meeting | Meetings | next meeting »

Dial in

 # Vidyo:
 # Phone:  650-903-0800 or 650-215-1282 x92 Conf# 9654 (US/INTL)
 #         1-800-707-2533 (pin 369) Conf# 9654 (US)
 # IRC:    irc://


  • Attendees: Jeff, Clint, Henrik, Cameron
  • This meeting:
    • Chair: Henrik
    • Notes: Clint

Last Weeks Action Items

  • [DONE] Clint: Fix the access issues with the vSphere client
  • [NEW] Stephen: Check if he has access to Room3.IDF
    • Clint will follow-up with Stephen if access is necessary
  • [DONE] Henrik: Change default for mozmill to use pprint-color (bug 768222)
  • [DONE] Henrik: Make the log() method a info() method and send info events to Mozmill (bug 767318)
  • [DONE] Clint: Run pprint-color with Windows
    • "Doesn't do anything bad"
  • [DONE] Jeff: Find/file bug for switching to mozlog (bug 739414)


  • Q3 Goals for the Automation Development crew
    • Finalize the Mozmill 2.0 code base (Python and Javascript)
    • Finish transition of automation scripts to use Mozmill 2.0
    • Get most of the API refactoring done (how much can we achieve?)
    • Start documentation of Mozmill testing (setup, how to code...)
    • Training of QA engineers how to use Mozmill for testing (bi-weekly vidyo sessions?)
    • Starting to create new Mozmill tests for major Firefox features
  • Check if using a Github mirror for mozmill-tests can increase the community participation
    • We would need an automatic two-ways sync solution
  • You can start working with the automation api for MozTrap now on staging []
    • Connector Docs: [1]
    • Connector Repo: [2]

Q3 2012 Goals Overview

Please mark topics which need to be discussed in the meeting as bold

Issues / Blockers

  • bug 770821 - Flash 11.3 with protected mode enabled hangs Firefox when application started by mozrunner and page with flash objects is opened
  • Restart test logic in Mozmill 2.0
    • As given by Jeff we want to have restart tests as a single module
    • Where should the restart logic be placed? test function or teardownTest?
      • If it's in the test function and a test fails we will not execute the restart
      • We currently can't put try/catch in the test function and do the restart in finally because we would mark the test as passed instead of failed. See bug 771511.
      • If in teardownTest we need global flags (stop vs. restart, reset profile) because its shared code between tests

Mozmill 2.0

  • bug 753752: No more waits between application startup and beginning of the first test. Thanks Clint!
  • bug 771517: User restart tests always report final results again (long time regression)
  • Blocker requests:

Mozmill 2.0 support for Automation Scripts

  • No updates

Mozmill Tests API refactor

  • No updates

Project Updates

Please mark topics which need to be discussed in the meeting as bold


  • Still waiting for ESX VM templates



  • Endurance tests have been added
  • Update tests will be available soon, once blockers have been solved


  • We now also report basic JS exceptions like the telemetry one

Tests and Shared Modules

  • Manifest files with skip/disable logic have been added to the mozmill-tests repository across branches


  • No updates


  • No updates

Personal Status

For the personal status please check the weekly status updates:

Meeting Notes

The meeting notes for this meeting can be read in the following etherpad:

Action items

  • [NEW] Clint: Check bug 770821 for the Flash 11.3 hang issue
  • [NEW] Clint: Check with Jason the rooms 3.IDF and 2.IDF for mozmill machines
  • [NEW] Clint: Add top level goal to pivotal tracker
  • [DONE] Henrik: Ask if we can add mintty to mozilla build
  • [NEW] Henrik: Check MozTrap connection for Mozmill test results
  • [NEW] Henrik: Put additional Q3 team goals into the pivotal tracker
  • [NEW] Henrik: Check restart tests that we bail out early if first test fails