QA/Test Automation/2010-07-28
< QA | Test Automation
Attendees
Last weeks action Items
- [DONE] Once Matt is back we will have to schedule meetings to finalize our team goals and personal goals
Projects
- Mozmill (Henrik)
- Test creation / shared modules (Henrik)
- Broken Tests
- Firefox 4.0 (Geo)
- Firefox 3.5/3.6 (Anthony)
- Singe failure resolved (Aaron):
- Unknown entity failure in testTewTab.js
- Lack of progress due to:
- Release testing (2 chemspills + 4.0b2)
- Focus on making tests local
- Singe failure resolved (Aaron):
- Update Tests (Henrik)
- MozMill Crowd extension (Henrik)
- Add-ons Testing (Henrik)
- (Release) Testing (Henrik)
- Result / Dashboard (Henrik)
Risky Goals
Personal
- Henrik
- Last two weeks
- Next two weeks
- Anthony
- Last two weeks
- 2 chemspill releases, 4.0b2 release
- 9 patch reviews
- Identified tests and new test-data for making tests local
- Lowest hanging fruit near check-in (11 new test pages)
- Next two weeks
- Get lowest hanging fruit tests converted to local:
- 29 tests can use existing test-data (including 11 new pages)
- 13 tests need to remain remote (ie. cert/connection error handling)
- 11 more technical
- Get lowest hanging fruit tests converted to local:
- Al
- Last two weeks
- Next two weeks
- Geo
- Last two weeks:
- Next two weeks:
- Aaron
- Last two weeks:
- Next two weeks:
- Adrian
- Last two weeks:
- Next two weeks:
Contributor Status
- Name
Roundtable
- General
- bug 582356 Location of Mozmill test related work on Bugzilla
- Separated Couchdb databases for release testing and crowd testing
- How long do we want to retain reports from crowd testing? 1 month?
- Issues
- Still hangs of Mozmill during test-runs on several machines (bug 571630)