QA/Desktop Firefox/Automation/Meetings:2011-12-12
< QA | Desktop Firefox | Automation
Jump to navigation
Jump to search
Mozmill Tests Team Meeting - December 12, 2011
Lead: Anthony Hughes (irc: ashughes) When: Every other Monday at 0800am PDT Telephone: 1.800.707.2533 password:369 conference:654 Vidyo: https://v.mozilla.com/flex.html?roomdirect.html&key=WBuu8ks3P4IZ
Previous Action Items
- ashughes
- [DONE] talk with David Burns, Dave Hunt, Vlad about WebQA automation process and how it can be adapted to Mozmill
- [DONE] propose new check-in model: Sandbox repo, Softvision shared modules development, shared reviews
- Softvision
Discussion Items
1. Do we want to start using tracking flags for patches? I suggest the following:
- status-firefox<N>: ?, unaffected, affected, fixed, wontfix
2. Q4 2011 -- how are we doing? where do we need to prioritize
- Failures: 8
- Endurance Tests: 1
- Restart Tests: 5
- Functional Tests: 5
- Open and Assigned: 37
- Open and Unassigned: 112
3. 2012 BHAGs -- what are they? let's define them...
- Endurance tests
- Backlog of open issues
- Smoketests
- Restart tests (ie. Add-ons related)
- Discussion
- need a community goal: growth, Mozmill Crowd evangelism / simplify
- clean up as part of a testday or work week
- no new tests which require extensive API writing, until Mozmill 2
- endurance tests include a percentage of dependencies
- point system for tests/fails/dependencies and track point progress
- workshops at colleges in Romania -- way to grow the community
- good-first-bug program for new contributors
Current Status
- Mozmill tracking spreadsheet
- Assigned Bugs: 37
- Resolved Bugs: 11 (last 2 weeks)
- Bugs waiting for review
- Been working on a new tracking spreadsheet to use starting 2012 -- will be sent around this week
- Been working on a new proposal for reviews to use starting 2012 -- will be sent around this week
- Old project documentation is nearly 100% migrated to it's new home under Desktop Firefox
Action Items
- Remus
- email dave hunt et al about GC in Endurance
- Anthony
- identify # of API changes complete/needed in Q4
- propose flags to qa-auto@
- figure out what tests don't need an API change and start a discussion
- come up with a P1 feature list for Endurance tests
- talk to Henrik about Crowd goals
- Vlad
- set up etherpad for Q1'2012 goals