QA/Ownership/Template
- The following document is a template for documenting feature ownership and testing
Contents
Feature Name
Summary
| Feature Summary | Description of the feature purpose and scope |
| Feature Owners | Names of people involved, provide IRC nicknames |
| Target Milestone | [status] Firefox N |
| Development Status | current status (YYYY-MM-DD) |
| QA Status | current status (YYYY-MM-DD) |
| Important Docs | Provide links to any important documents, wikis, blog posts, and tracking bugs |
Milestone Sign-off
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone.
| Milestone | Assessment |
| Nightly | YYYY-MM-DD: [status] Assessment of feature readiness for the Nightly Tester audience |
| Aurora | YYYY-MM-DD: [status] Assessment of feature readiness for the Aurora Tester audience |
| Beta | YYYY-MM-DD: [status] Assessment of feature readiness for the Beta Tester audience |
| Release | YYYY-MM-DD: [status] Assessment of feature readiness for the Release audience |
Developer:QA Review
The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:
- Do we have automated tests for the feature?
- What do they cover?
- What do they not cover?
- How well do they cover the feature?
- What are the important areas we should focus on?
- What are the dependencies?
- What is our comfort level with this feature in its current state?
- What feedback would you like from QA?
Security Review
The QA person responsible for the feature should ensure she attends the security review, if one is scheduled, and be involved in that process. Collect any bugs and feedback in the test plan so that any necessary security-related testing can be captured.
Privacy Review
The QA person responsible for the feature should ensure she attends the privacy review, if one is scheduled, and be involved in that process. Collect any bugs and feedback in the test plan so that any necessary privacy-related testing can be captured.
Quality Management
The following section details the state of qualification of the feature.
| Area of Coverage | Description | Status |
| Use Cases | Status of quality coverage and readiness of scoped usecases (provide links) | [status] (YYYY-MM-DD) |
| Beta Testing | Status of beta tester engagement initiatives (provide links) | [status] (YYYY-MM-DD) |
| Localization | Status of l10n coverage and readiness (provide links) | [status] (YYYY-MM-DD) |
| Accessibility | Status of a11y coverage and readiness (provide links) | [status] (YYYY-MM-DD) |
| Plugin Compatibility | Status of quality coverage and readiness of feature interaction with plugins (provide links) | [status] (YYYY-MM-DD) |
| Addon Compatibility | Status of quality coverage and readiness of feature interaction with top add-ons (provide links) | [status] (YYYY-MM-DD) |
| Top-site Compatibility | Status of quality coverage and readiness of feature interaction with top websites (provide links) | [status] (YYYY-MM-DD) |
Bug Management
| Bugs | Description | Status |
| Tracking Bugs | Bugs tracking feature development | [status] (YYYY-MM-DD) |
| VERIFYME | Fixed bugs requiring verification | [status] (YYYY-MM-DD) |
| UNCONFIRMED | Unconfirmed bugs requiring confirmation | [status] (YYYY-MM-DD) |
| QAWANTED | Bugs requiring further QA testing | [status] (YYYY-MM-DD) |
Manual Tests
The following section details the state of tests for this feature.
| Tests | Description | Status |
| MozTrap Smoketests | Manual testcases in MozTrap to be run for minimal qualification | |
| MozTrap BFT/FFTs | Manual testcases in MozTrap to be run for detailed qualification | |
| MozTrap Regression Tests | Manual testcases in MozTrap to cover known regressions |
Automated Tests
| Tests | Description | Status |
| Mozmill Tests | Automated tests in Mozmill run in CI or on-demand (provide links) | |
| Developer Tests | Automated tests in other frameworks run on check-in (provide links) |
Community Engagement
The following is a list of community engagement initiatives (testdays, meetups, etc) to involve volunteers in testing and providing feedback on this feature.
| Date | Event | Status |
| YYYY-MM-DD | Name of event and description of purpose | [status] |
