QA/Test Automation/2011-01-12

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

Last weeks action Items

• Geo: Update documentation for handling of failing Mozmill tests
• Anthony: Update coding styles and keep discussion on-going to get remaining important rules defined

Goals Overview

• Q4 goals
• Q1 goals planning

Project Status

Panorama Tests (Anthony/Al)

• 4 / 15 doable tests currently in development/review
• 6 tests currently blocked by drag & drop (bug 515776)
• Will be looking for team assistance once 4.0b9 work dies down (early next week)
• Proposed Team Goal: All non-blocking tests automated

Triggered software updates (Geo/Henrik)

• Short updates

Mozmill Crowd Extension (Henrik/Aaron)

• Short updates

Endurance Tests (Dave/Aaron)

• Update project page with notes from this week's meeting
  • Project page: https://wiki.mozilla.org/QA/Mozmill_Test_Automation/Endurance_Tests
  • Meeting notes: http://etherpad.mozilla.com:9000/endurance-tests-10-01-11

Redesign Shared Modules (Geo/Henrik)

• Short updates

Mozmill Result Dashboard (Henrik/Anthony)

• Short updates

Build bot - local data (Anthony/Aaron)

• No status
• Most likely will not see progress this quarter due to Firefox 4 work and Automation priorities

Others

DOM Walker + L10n API (Adrian)

• Short updates

Tests / Shared Modules

• General (Henrik)
  • Short updates

• Test Refactoring (Anthony)
  • project in place to begin once Firefox 4b9 work dies down
  • will need team assistance to complete everything this quarter (please let me know if you are willing to help)
  • we still have a few outstanding items for discussion
    • if possible, I'd like to discuss these during the team meetings (resolve 1 per meeting)
    • agreement would be integrated into refactoring, not styleguide

• Broken Tests
  • Firefox 4.0 (Geo)
    • Short updates
  • Firefox 3.5/3.6 (Anthony)
    • Focusing on 4.0 failures for b9 release
    • Will focus on branch failures once b9 is out

Automation Scripts / Infrastructure

• • Short updates

Personal Status

For the personal status please check the weekly status updates:

• 110103 - 110107
• 110110 - 110114

Roundtable

General

• Styleguide & Refactoring
  • we should fork into two separate projects
  • freeze the styleguide
  • new additions go into refactoring work
  • changes/additions to styleguide should reflect "style" not logical/design changes
• Failures
  • adopt a module-ownership model to deal with all failures (4.0, 3.6, and 3.5)
  • once we are green, go back to a branch-based model or stay with module-ownership?

Issues