QA/Test Automation/2011-04-20

From MozillaWiki
Jump to navigation Jump to search

previous meeting | Meetings | next meeting »

Dial in

 # 650-903-0800 or 650-215-1282 x92 Conf# 315 (US/INTL)
 # 1-800-707-2533 (pin 369) Conf# 315 (US)
 # irc.mozilla.org #mozmill for backchannel

Attendees

Last weeks action Items

  • Matt: Invite mrz into the QA staff meeting (possible during the QA workweeks staff meeting?)

Goals Overview

Risky Goals

Project Status

Redesign Shared Modules (Geo/Henrik)

  • Henrik: Working on window wrapper and handler. Want to finish it by next week
  • Removed 3rd party inheritance class and ported existing code to new classes
  • Doc tags still broken with new classes, need to figure out proper tagging
  • Test porting resumes this week

On-demand update tests (Geo/Henrik)

Endurance Tests (Dave/Anthony)

Others

Mozmill Crowd

  • Planning and scheduling 0.2 release
  • Request for a general icon we can use everywhere from Design team (bug 649450)

Dashboard

  • Started planning for the Elastic Search work
    • Possible candidate for help could be Owen Coutts

On Demand Provisioning (Cloud Automation) (Al/Henrik)

Tests / Shared Modules

General (Henrik)
Broken Tests
  • We are clean again after the check-in of the temporary workaround of the Panorama DTD fallout.

Shadow web server (Al/Henrik)

Automation Scripts / Infrastructure (Henrik)

  • Working on the download script for daily builds (Nightly, Aurora)

Personal Status

For the personal status please check the weekly status updates:

Roundtable

General
  • Handling of Mozmill tests in Q2
    • Before the API is ready, we would like to start with tests for the Discovery pane in the Add-ons Manager
      • Krupa already has been started to create tests in Litmus
      • Tests in that area have lesser impact to any API refactoring changes.
    • Once basic new API is ready, Geo would like to have feedback from Waverly folks
    • We will start to built-up the maps and shared modules for the browser window and the add-ons manager tab
    • New tests will be written against the new UI, and exiting tests for the AOM can be ported.
    • Owners will take care of tests in their area for porting (we will not be able to port all existing tests)

Meeting Notes

Action items