QA/Test Automation/2011-06-01

From MozillaWiki
< QA‎ | Test Automation
Revision as of 09:37, 1 June 2011 by Whimboo (talk | contribs) (Created page with "<small>previous meeting | Meetings | next meeting »</small> =Dial in= # 650-90...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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 action items

  • Geo: Work with Al and Anthony to get the on-demand update testing running on qa-set (April 27th)
  • [DONE] Henrik: Talk to David for a meeting about handling patch reviews with Softvision (include Web Automation)
    • It will not happen before Henrik comes back from vacation
  • [DONE] Henrik: Create automation scripts for handing new test-run called "remote" (May 19th)
  • Anthony: Get in contact with Vlad by end of today to kick of Discovery Pane tests (May 18th)
  • Dave: Please reference last meeting notes from endurance meeting if you can't attend
  • Al: Collect possible use cases and goals on-demand provisioning
  • Al: Create remaining invalid certificates (May 20th)

Goals Overview

Risky Goals

Project Status

Redesign Shared Modules (Geo/Henrik)

On-demand release tests (Geo/Henrik)

  • Anthony has discovered issues with the daemon yesterday during release testing. We had to fallback to the old way of running update tests

Endurance Tests (Dave/Anthony)

Others

Mozmill Crowd

  • Patch for further launch points (add-on bar, Firefox button) has been landed
  • Working on the documentation and the version checker for test environments

Dashboard

  • TBD

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

Tests / Shared Modules

General (Henrik)
Broken Tests
  • All broken functional tests have been fixed for branches down to 4.0
  • Endurance test for Tab Switching in Panorama is still failing - we really have to ensure to get those kind of failures fixed faster
Softvision (Anthony)

Shadow web server (Al/Henrik)

Automation Scripts / Infrastructure (Henrik)

Personal Status

For the personal status please check the weekly status updates:

Roundtable

General
  • To ensure a fast progress please work on action items right after the meeting, or at least get the process triggered. Doing that 1 or 2 days before the next meeting will push us back by nearly 2 weeks. (Henrik)
  • We have to get better in fixing broken tests. We can't leave broken ones failing for over two weeks! (Henrik)

Meeting Notes

Action items

  • Geo: Send pivotaltracker details for API refactoring project to team members
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Test_Automation/2011-06-01&oldid=314435"