Feature (example: add-ons preference UI)
- Development Status: - In progress (date)
- Feature Testing: - In progress (date)
- Team: Olli Pettay (smaug), Matt Evans (mevans)
- Tracking Bugs:bug 472529 - (websocket) Support for Web sockets' HTML5 Draft Recommendation
Feature Description
Brief description of the feature listed here.
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone. Each milestone link references a section below that discusses the criteria and evaluation that went into the QA go/no-go decision.
top
top
top
The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what should be covered. If it is not covered, list it as not covered.
Note: not all items listed below will apply for a given feature
Test Item
|
Description
|
Covered By
|
Status
|
Item 1
|
Item 1 Description
|
Developer Tests
|
|
Item 2
|
Item 2 Description
|
Beta tester exposure
|
|
#Localization
|
Feature localization
|
|
|
#Accessibility
|
Feature accessibility
|
|
|
#Plugins
|
Plugins compatibility
|
|
|
#Addons
|
Addons compatibility
|
|
|
#Topsites
|
Top internet sites compatibilities
|
|
|
top
top
Item
|
Description
|
Status
|
#Testdays
|
Links to test day event results for feature
|
|
#Bugdays
|
Links to bug day event results for feature
|
|
#Meetups
|
Links to Meetup events for feature
|
|
top
Project Wiki
- Provide link to all project related wikis
top
Developer Links
- Provide links to all feature related developer links to blogs and other internet sites
top
Other Docs
- Provide links to all feature related developer links to blogs and other internet sites
top
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?
top
Beta1
Beta2
Beta3
Bug Tracking
- Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
Query Name
|
Description
|
Bug bug 570789 - Add WebSocket support to mochitest
|
blocking bug for websockets
|
Bug bug 562681 - Update the WebSockets implementation to support the latest version of the protocol
|
|
top
Bug Verification
- Feature bugs that need verification
top
Bug Triage
top
Localization
- Details of feature localization test requirements
top
Accessibility
- Details of feature accessibility test requirements
top
Plugins
- Details of plugins compatibility test requirements
top
Addons
- Details of addons compatibility
top
Topsites
- Details of top internet sites test requirements
top
Developer Tests
- Links to automated developer tests
top
Mozmill Tests
If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "[mozmill-test-needed]" whiteboard entry to the feature implementation or regression bug.
List of Mozmill Tests:
- Links to automated mozmill feature test cases
top
Smoke_Tests
- links to litmus smoke tests or description
top
Regression_Tests
- links to litmus BFT and/or regression tests description
top
Functional_Tests
- links to litmus FFT and/or complete functional tests description
top
Testdays
- Links to test day event results for feature
Bugdays
- Links to bug day event results for feature
Meetups
- Links to Meetup events for feature