QA/Automation/Meetings/120319

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

previous meeting | Meetings | next meeting »

Dial in

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

General

  • Attendies:
    • Henrik
    • David Burns
    • Dave Hunt
    • Clint Talbert
    • David Guo
    • Cameron
  • This meeting:
    • Chair: Henrik Skupin
    • Notes: Cameron Dawson

Last Weeks Action Items

  • [CARRY OVER] David Burns: Will Send summary of infrastructure duties/tasks to team
  • [DONE] David Burns: Investigate team blog on mozilla.org
    • Henrik will continue on it
  • [DONE] David Burns: Finalize how to record daily work logs - Will be discussed next week
  • [DROPPED] David Burns: Update _AutomationBot to handle scrum
  • [DONE] Cameron: Think about a way how to reach out to the community for naming ideas
  • [DONE] Henrik: Talk to Clint regarding our own blog and keep things going
    • Will be discussed in one of the next a-team meetings. Not sure if we want to go this way or via the A-team planet

Roundtable

  • Importance of highlight section in scrumpads for Mozilla weekly all-hands meeting (Henrik)
  • Slow down in feedback on questions of top projects over the last couple of weeks (Henrik)

Goals Overview

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

Issues / Blockers

  • No updates

Remote Mechanism to trigger Mozmill tests for Firefox releases (Geo)

  • No updates

CI system for daily and l10n Firefox Builds (Henrik)

  • Specific testruns will be triggered for different branches as given by the configuration
  • Nodes have been added for all testing platforms on Windows, Linux ones are left to do
  • Next create code to distribute tests across those machines

Mozmill 2.0 support for Automation Scripts (DavidG)

  • Waiting on feedback.

Data Validation Method for Mozmill Dashboard (DavidB)

  • Waiting on feedback from the team. Only DaveH has replied so far

MemChaser

Job Page for Community Members (DavidB)

  • No updates

Weekly Blog Posts (Rotating)

Project Updates

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

Endurance Tests

Current Work

  • In Progress
    • Framework
    • Tests
      • bug 705284 - Mozmill endurance test for bookmarking all tabs and opening and closing them
      • bug 711360 - Mozmill endurance test for opening new window
      • bug 711129 - Mozmill endurance test for Open & Close a popup window
  • Landed Recently
    • Framework
    • Tests
  • Backlog
  • Regressions
    • bug 724553 - Memory usage spike detected in Mozmill Endurance tests for Mac OS X 10.6.8 x86_64
      • Caused by incremental garbage collection. We need to follow these up as a high priority, CC the appropriate people, and add the MemShrink whiteboard tag
  • Failing Tests
    • bug 671476 - Mozmill endurance test for loading a SWF video via URL
    • bug 671479 - Mozmill endurance test for loading a SWF video via iframe
    • bug 707663 - Timeout failure in /testTabbedBrowsing_PinAndUnpinAppTab/test1.js | Tab has scrolled into view

Discussion Items

Infrastructure

  • No updates

Case Conductor (Cameron)

  • Working on new name search
  • Processing user feedback
  • Working toward 3/30 1.0

Mozmill

Feedback from Firefox Desktop Automation team

  • No updates

Shared Modules

  • No updates

API Refactor

  • No updates

Automation Scripts

  • No updates

Dashboard

  • No updates

Mozmill Crowd

  • No updates

On-demand Testing

  • No updates

Selenium

  • (DB) Working on WebDriver spec this week

Other

  • Nightly Tester Tools 3.2.2 under review on AMO - will be released soon

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

  • [CARRY OVER] David Burns: Will Send summary of infrastructure duties/tasks to team
  • [NEW] Clint: come up with goals proposal
  • [NEW] Dave Hunt: document steps for people when they hit a memory spike
  • [NEW] All: respond to feedback requests for goals
  • [NEW] All: formulate project and individual Q2 goal ideas and send to Clint