QA/Test Automation/2010-09-08

previous meeting | Meetings | next meeting »

Last weeks action Items

• Geo: Schedule meeting for debugging/execution labs for automation
• Geo: Send out list of broken tests w/ Fx4 and MM1.5
• [DONE] Henrik: Update QA lab machines and databases to use Mozmill 1.5 (Sep. 1st)
• [ON TRACK] Henrik: Send out email for more details to introduction (recruiting) video
  • Waiting for feedback of the presentation brainstorming ideas first
• [DONE] Henrik: Send out email to start the work for the automation presentation
• [DONE] Henrik: Schedule meeting for release tasks and machine reservation
• [DROPPED] Henrik: Setup a list of prioritized feature requests for 2.0
  • Will work together with the A-team during our work week
• Matt: Check what limits test harnesses on buildbot to use other local webservers (connect with John O'Duin)
• [DONE] Matt: Request a post mortem for Mozmill 1.5
• All: Check the proposed docs for the shared module refactoring from Geo

Projects

Mozmill (Henrik)

• Notes from the Mozmill 1.5 Post Mortem

Test creation / shared modules

• General (Henrik)
  • Currently working on updating the AddonsAPI for Firefox 4.0
• DOM Walker + L10n API (not ready yet) (Adrian)
  • Documentation + UML Diagrams for CommonA11yL10nAPI and L10nAPI
  • implementation of the CommonA11yL10nAPI and L10nAPI
  • Targeting the end of September for all the L10n work completion

Local Test Data (Anthony)

• No update
• Progress slow due to heavy release work (4.0b5, 3.6.9, 3.5.12)
• Workflow Tweak:
  • Aaron write patches
  • Anthony review/check-in patches

Broken Tests

• Firefox 4.0 (Geo)
  • Broken tests are still broken, re: missed goal in personal section below.
  • Have started test runs with Mozmill 1.5 final, will be generating new bugs/fix list from those runs.
• Firefox 3.5/3.6 (Anthony)
  • No update

Update Tests (Henrik)

MozMill Crowd extension (Henrik)

• no update

Add-ons Testing (Henrik)

• no update

Automation (Henrik)

• Backed-out canonical path generation for reporting. It will be part of the couch database.

Dashboard (Henrik)

• Creation of specs have been started; first revision passed
• Created staging server to work with until problems (reliability and reversed proxy) with Brasstacks are solved.
• Separated testrun results into different sections
• Layout updated

Personal

Henrik

• Last two weeks
  • [MISSED] Update AddonsAPI and tests to work with Firefox 4.0
    • Had to wait for major UI changes and patch stabilization
  • [MISSED] Create list of Mozmill tests to implement
  • [DONE] Create spec for the dashboard (General test-run pages)
  • Started to work on the new version of the dashboard
• Next two weeks
  • Finish work on the dashboard (general testrun)
  • Continue work on the crowd extension
  • Update AddonsAPI and prepare list of Mozmill tests to implement
  • Attend CouchCamp and QA work week

Anthony

• Last two weeks
  • [MISSED] Complete conversion of 31 tests to use local-data
    • Heavy release schedule and preparation for workweek bugday
• Next two weeks
  • Review queue to 0
  • Check-in queue to 0
  • Restructure workflow of local-data project

Al

• Last two weeks
  • Get script for Bug 553618 re-fixed and submitted.
  • Figure out what we can do with microsummary restrictions.
• Next two weeks

Geo

• Last two weeks:
  • Generating functioning prototypes for refactored UI modules
  • Collecting team feedback re: prototypes
  • [CARRY OVER] Fixes for bug 573582, bug 573584, bug 575250
• Next two weeks:

Aaron

• Last two weeks:
  • [CARRY OVER] of conversion of 31 tests to use local-data
  • Refactoring tasks in tests for 1.5
  • Patches for 4.0b* broken tests
• Next two weeks:
  • [CARRY OVER] of conversion of 31 tests to use local-data (patches and fixes upon reviews)
  • Attend QA work week

Adrian

• Last two weeks:
  • See under shared module work
• Next two weeks:

Contributor Status

• Name

Roundtable

General

• QA Automation (recruiting) video
  • Finalize details (please send Henrik the presentation proposals so we can draft what we want to say)

Issues

• Brasstacks is not reliable enough and with the use of reversed proxies (databases are located under /couchdb/ instead of /) we run into troubles when using vhosts.