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

• Matt, Geo, Anthony, Aaron, Henrik, Adrian

Last weeks action Items

• Geo: [CARRY OVER] Send out list of broken tests w/ Fx4 and MM1.5
  • Intentionally [MISSED] -- does new Dashboard already cover us here?
• Geo: schedule in-IRC meeting to do patch-handling proposal
  • [DONE] Email sent out Monday starting convo, asking for venue. Let's settle venue today
• Geo: [CARRY OVER] Generate wiki page to sum up tab candy objective
  • [MISSED] Wasn't aware this was still needed, please clarify.
• Henrik: Talk with John O'Duin about specifics of the test environment
• Henrik: [DONE] Setup IRC channel #mozmill + Mailing list (qa-auto) [bug 598883]
• Henrik: [DONE] Send out goals proposals for final rework
• Matt: [CARRY OVER] Action items from release tasks meeting? Need to notify release leads that they're responsible for coordinating resources.

Goals Overview

• Current status for Q3 goals
  • [MISSED] Ship Mozmill Crowd v0.3 to our tester and localizer community
  • [DONE] Implement the first version of the Web Dashboard for test results
  • [DONE] Create a solid model for re-designing the shared modules
  • [DONE] Create a set of high priority BTFs for one or more main features of Firefox 4.0
  • [MISSED] Implementation of a DOM walker (shared module) to allow l10n and accessibility tests

• Planning for Q4 (proposals)
  • QA Q4 goals

Projects

Mozmill (Henrik)

• Mozmill 1.5.1 still targeted for end of this week
  • Will included patches to allow Mozmill execution on buildbot
  • Contains a fix for a long outstanding bug in waitForPageLoad for error pages bug 602040 (will fix about 9 broken tests across branches)
  • Work to get the expected event patch landed for this release bug 583604, which also offers a general mouse event helper function to synthesize mouse events with modifier keys.

Test creation / shared modules

• General (Henrik)
  • Completed the rewrite of the AddonsAPI for Firefox 4.0 (still dependencies to existing Firefox bugs)
  • Created a nodeCollector class to make element retrieval as easy as possible (querySelector)
• DOM Walker + L10n API (Adrian)
• Redesign Shared Modules (Geo)
  • Initial two tests + supporting code pushed. Please see Personal Repo

Local Test Data (Anthony)

• Phase I complete: 35 tests local
• Phase II: developing plan of action for more technical tests

Broken Tests

• Firefox 4.0 (Geo)
  • No update due to Q3 goals rush. High priority going into Q4.
• Firefox 3.5/3.6 (Anthony)
  • Missed last quarter
  • 25 failures to be resolved this quarter (top priority)

Update Tests (Henrik)

• For now we do not upgrade the SoftwareUpdateAPI to handle the about window. We need final feedback from Beltzner first.
• Software update tests have to be updated to collect meta data as array to allow multiple update steps

MozMill Crowd extension (Henrik)

• No update

Add-ons Testing (Henrik)

• Presently working on Add-on tests module revisions that make use of the new Add-on API (Aaron)

Automation (Henrik)

• No update

Dashboard (Henrik) staging server

• Finished implementation of the general test-run pages (please give me feedback)
• Filtering has been solved, the only limitation we have is that only one range filter can be used against the database.

Risky Goals

Personal

Henrik

• Last two weeks
  • [DONE] Finish work on the dashboard (general testrun)
  • Depending on the goals we want to achieve this quarter:
    • [DROPPED] Continue work on the crowd extension
    • [DONE] Update AddonsAPI and prepare list of Mozmill tests to implement
• Next two weeks
  • Make sure our requested / needed features will land for Mozmill 1.5.1
  • Update Software update tests to collect meta data as array
  • Update shared modules to use Common JS
  • Continue work on the crowd extension
  • Prepare proposal for my talk at the Selenium meetup in London

Anthony

• Last two weeks
  • [DONE] Ensure 10 remaining local-data tests complete
• Next two weeks
  • Develop action plans for this quarter:
    • Local Data Phase II
    • Refactoring Tests Phase I
    • Branch Failures

Al

• Last two weeks
  • Going to Bali.
• Next two weeks

Geo

• Last two weeks:
  • Covering for Al, so wasn't full time on auto.
  • [DONE] One more test for refactor project, from AwesomeBar
  • Code reviews, comments, etc.
  • Conversation started re: sheriff/pool for checkins
  • Conversations started re: coding standards
• Next two weeks:
  • Bug fixes for 4.0 tests (!!)
  • At least one more test (non-AwesomeBar) for the refactor examples
  • Distillation of examples to templates/instructions
  • Starting "daily standup" emails sometime this week. Hope for full team participation once we see the usefulness.

Aaron

• Last two weeks:
  • [DONE] Conversion of tests to utilize local data - Phase I
• Next two weeks:
  • Presently working on Add-on tests module revisions that make use of the new Add-on API
  • Fixing up 4.0 branch broken test failures
  • Work with Anthony in ascertaining preliminary action steps and beginnings for test refactoring and local data, phase II

Adrian

• Last two weeks:
  • [MISSED] implement the L10n tests for the update window
  • [CARRY OVER] bring the 2 shared-modules and 4 tests through the reviews
• Next two weeks:
  • implement the L10n tests for the update window
  • bring the 2 shared-modules and 4 tests through the reviews

Contributor Status

• Name

Roundtable

General

Issues

• Brasstacks - Reverse Proxy
  • Dashboard driven by Sammy JS doesn't work OOTB. Eventually we can circumvent the reverse proxy issue. Will have to wait with testing for the upgrade to CouchDB 1.0.1, which will happen this week.
• Mailing List
  • How are we liking qa-auto for issue discussion? Too much mail, or useful?
• [matt] Request for automated update testing for nightlies

Meeting Notes

• Goals
  • Use the U-Test community to run tests with the Mozmill Crowd extension
• Others
  • Discussion for patch-handling proposal will happen on the mailing list; If needed we can schedule a conf meeting to finalize the proposal

Action Items

• Anthony: Send link to the failure spreadsheet for the overview of failed tests
• Geo: [CARRY OVER] Generate wiki page to sum up tab candy objective
• Geo: [DONE] Coordinate integration of the memory into qa-horus and qa-set
• Henrik: [MISSED] Talk with John O'Duin about specifics of the test environment
• Henrik: [DONE] Talk with Clint if mozmill-dev mailing list can be used for QA Test Automation activities
  • Yes we can use this list for our Mozmill tests topics. It will result in more openness and we can combine all efforts around Mozmill.
• Henrik: [NEW] Find a way to get a notification for builds on FTP for Mozmill
  • Asked on bug 588398 but no reply yet
• Matt: [DONE] Action items from release tasks meeting? Need to notify release leads that they're responsible for coordinating resources.