previous meeting | Meetings | next meeting »

Dial in

 # Vidyo:  https://v.mozilla.com/flex.html?roomdirect.html&key=PGtLpx3XQGJz
 # Phone:  650-903-0800 or 650-215-1282 x92 Conf# 9654 (US/INTL)
 #         1-800-707-2533 (pin 369) Conf# 9654 (US)
 # IRC:    irc://irc.mozilla.org:6697/#automation

General

• Attendees:
  • Stephen Donner
  • Dave Hunt
  • Henrik Skupin
  • Clint Talbert
  • Jeff Hammel
• This meeting:
  • Chair: Dave Hunt
  • Notes: Henrik Skupin

Last Weeks Action Items

• [DONE] Henrik: Check if log() method is still broken.
  • This works fine in tests but I have another proposal. See below in roundtable.
• [DONE] Clint: Create templates for all the VMs.
• [DONE] Henrik: Update wiki with details of Mac OS X 10.8 media and destination hardware location.
• [DONE] Henrik: Fix the Automation Developer/Development discrepancies on the wiki.
• [DONE] Henrik: Raise QA training sessions for Mozmill test development in QA staff meeting.

Roundtable

• Some questions about enhancements for Mozmill 2:
  • Shall we enable pprint-color for Mozmill CLI by default? This would help all of our contributors in running tests and reporting brokenness. Automation tools whould make use of the --console-level option and select json.
  • What should we define as test report? Right now we send pass/fail on each single test, even for clicks, keypresses and others. Shall we change this to expect/assert calls only? Do we want to report passed clicks as info entries? That way we can make the test module result a 'Test End' event and report the timing instead of the pass/failure - similar to Mochitest.

Q2 2012 Goals Overview

• https://wiki.mozilla.org/Auto-tools/Automation_Development#Prioritized_Projects

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

Issues / Blockers

• ESX box is down again. See bug 757421
• Strange Application disconnect errors with Mozmill 1.5 - what to do? See bug 767820

Mozmill 2.0

• Fixed a couple of issues for user restart tests - only one or two known issues are remaining
• Started refactoring of Mozmill Python code to make it easier to use the API
• Changed the way how we log entries to the console. Check this out it looks awesome especially with pprint-color!
• Mutt has been changed so JS tests don't get run in isolation mode by default. That caused us some regressions Mutt hasn't reported
• All files in the Mozmill repository are PEP8 conform now!
• Blocker requests:
  • mozmill-2.0?
  • mozmill-2.0+

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

Infrastructure

• Waiting for ESX VM templates.

Mozmill

Automation

• In Mozmill CI we now store screenshots for l10n failures as artifacts in Jenkins. We have to figure out how to make those available by the public. Probably upload them to Henrik's people account.

Dashboard

• No updates

Tests and Shared Modules

• No updates

Selenium

• No updates

Add-ons

• Some landings for Nightly Tester Tools which include new features.

Personal Status

For the personal status please check the weekly status updates:

• 120625 - 120629

Meeting Notes

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

• http://etherpad.mozilla.com:9000/automation-developer-meeting-20120625

Action items

• [NEW] Clint: Fix the access issues with the vSphere client
• [NEW] Stephen: Check if he has access to Room3.IDF
• [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"
• [NEW] Jeff: Find/file bug for switching to mozlog