|
THIS PAGE IS A WORKING DRAFT | 
|
| The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page. |
This is both the agenda and the goals landing page for the Test Development and Automation team for Q2 2009. This is not official yet. It is in draft form.
Test Automation
Proposal (ctalbert): Greening Tinderboxes
- Institute a measuring system for tinderbox realibility
- Debug the known, observed, random failures, create a plan for handling random failures going forward.
Proposal (ctalbert): Close loop on Automation Suites
- Is there automation work required for JS Tests?
- Enable Build/Test infrastructure to run Mozmill tests (unit tests at least)
- Have Mozmill tests running automatically, reporting to results server and/or staging tboxes (as appropriate)
- Integrate Maemkit with Tinderbox, hand off to build
Test Development
Proposal (ctalbert): Expanding Test Coverage
- Shared Team Goal to increase test coverage by X amount, where X is a measurement of reducing in-test-suite-? areas and improving code coverage numbers on previously untouched pieces of code.
- Use code coverage results to identify functions within each team member's code area that are not covered well (< 40%)
- Attempt to identify any in-test-suite-? bugs that also address this area
- Create a list of the Y most wanted tests from the intersection of these points
- Write those tests to target those lines of code and/or the address the concerns raised w.r.t. to the in-test-suite-? flag
Community Leadership
Proposal (ctalbert): Use the "Most Wanted List" to expand code coverage
- Take the "Expanding Test Coverage" goal's "most wanted list" in each area and invite QA Community members (via QMO) and Development Community Members to help address these areas. This is crucial as most of the time we'll need the dev community to tell us how to write these tests anyway, so it makes sense for them to be working on these alongside us.
Test Tools
Proposal (ctalbert): Release a redesigned QAC
Proposal (ctalbert): Mozmill 1.2 (or 1.1.1) Maintenance Release
Proposal (ctalbert): Results Server Should be Reporting Mozmill Results