Firefox/Projects/Async Places containers/Test Plan: Difference between revisions
< Firefox | Projects | Async Places containers
Jump to navigation
Jump to search
| Line 173: | Line 173: | ||
| [[#Testdays]] | | [[#Testdays]] | ||
| Links to test day event results for feature | | Links to test day event results for feature | ||
| | | none | ||
|- | |- | ||
| [[#Bugdays]] | | [[#Bugdays]] | ||
| Links to bug day event results for feature | | Links to bug day event results for feature | ||
| | | none | ||
|- | |- | ||
| [[#Meetups]] | | [[#Meetups]] | ||
| Links to Meetup events for feature | | Links to Meetup events for feature | ||
| | | none | ||
|} | |} | ||
[[#Feature_Description|top]] | [[#Feature_Description|top]] | ||
Revision as of 23:56, 24 June 2010
Asynchronous Places Containers
- Development Status: - STALLED (06/24/2010)
- Feature Testing: - NOT STARTED (06/24/2010)
- Team: adw (dev), ashughes (qa)
- Tracking Bugs: bug 490714
Feature Description
Places containers currently use on-main-thread Storage APIs to get data from the Places database. This project will replace those calls with off-main-thread calls. Places containers include bookmark folders, history containers, tags, and bookmark and history searches and queries.
Feature Release Readiness Assessment
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone.
| Milestone | Assessment |
|---|---|
| #Beta1 | NO GO |
| #Beta2 | N/A |
| #Beta3 | N/A |
Feature Documentation
| Item | Description | Status |
|---|---|---|
| #Project_Wiki | Wiki Links to all feature related entries | [DONE] |
| #Developer_Links (blogs) | Developer links to feature related sites | pending-feedback |
| #Other_Docs | Web links to feature related sites | pending-feedback |
| #Developer_QA_Review | Details from developer and qa discussions regarding feature test strategies and issues. | [DONE] |
Feature Bug Management
| Item | Description | Status |
|---|---|---|
| #Bug_Tracking | Top level bugs tracking feature | [DONE] |
| #Bug_Verification | Feature bugs that need verification | pending-feedback |
| #Bug_Triage | Links triage bug tasks | pending-feedback |
Feature Test Items
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.
| Test Item | Description | Covered By | Status |
|---|---|---|---|
| #Frontend | UI Changes, Bookmarks Manager, History, etc | Developer (browser-chrome tests), QA (Regression testing) | NOT STARTED |
| #Backend | Backend changes to the API | Developer (xpcshell tests) | NOT STARTED |
| #Localization | Feature localization | pending-feedback | |
| #Accessibility | Feature accessibility | pending-feedback | |
| #Plugins | Plugins compatibility | pending-feedback | |
| #Addons | Addons compatibility | pending-feedback | |
| #Topsites | Top internet sites compatibilities | pending-feedback |
Feature Tests
Automated Tests
| Item | Description | Status |
|---|---|---|
| #Developer_Tests | Links to automated developer tests | pending-feedback |
| #Mozmill_Tests | Links to automated mozmill feature test cases | incomplete |
Manual Tests
| Item | Description | Status |
|---|---|---|
| #Smoke_Tests | link to smoke tests | pending-feedback |
| #Regression_Tests | link to BFT and/or regression tests | pending-feedback |
| #Functional_Tests | link to FFT and/or complete functional tests | pending-feedback |
Community Test Events
| Item | Description | Status |
|---|---|---|
| #Testdays | Links to test day event results for feature | none |
| #Bugdays | Links to bug day event results for feature | none |
| #Meetups | Links to Meetup events for feature | none |
Feature Documentation Details
Project Wiki
Developer Links
Other Docs
Developer QA Review
- Do we have automated tests for the feature?
- Not yet, but we will
- What do they cover?
- Backend API changes
- UI changes
- Code coverage
- What do they not cover?
- Functionality of related features (bookmarks, history, etc)
- How well do they cover the feature?
- No coverage from QA needed apart from regression testing for Bookmarks, History, etc
- What are the important areas we should focus on?
- UI
- Bookmark Manager
- History
- What are the dependencies?
- n/a
- What is our comfort level with this feature in its current state?
- Feature is not ready, but is not a "called-out" feature of Firefox 4
- What feedback would you like from QA?
- Keep an eye out for regressions via release-cycle testing
Feature Release Readiness Assessment Details
Beta1
- Will not be ready for Beta 1
- May or may not be ready for Firefox 4 final
Beta2
Beta3
Feature Bug Management Details
Bug Tracking
| Query Name | Description |
|---|---|
| bug 490714 | Top-level tracking bug |
Bug Verification
- Feature bugs that need verification
Bug Triage
- Bug triage information
Feature Test Items Details
Frontend
- UI changes
- Bookmarks regressions
- History regressions
Backend
- Bookmark Manager regressions
- History regressions
- Performance regressions
Localization
- Details of feature localization test requirements
Accessibility
- Details of feature accessibility test requirements
Plugins
- Details of plugins compatibility test requirements
Addons
- Details of addons compatibility
Topsites
- Details of top internet sites test requirements
Feature Tests Details
Automated Tests Details
Developer Tests
- Links to automated developer tests
Mozmill Tests
- Bookmarks
- History
- Library
Manual Tests Details
Smoke_Tests
Regression_Tests
Functional_Tests
Community Test Events Details
Testdays
- No testdays planned
Bugdays
- No bugdays planned
Meetups
- No meetups planned