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.
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone.
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.
| 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
|
|
|
| #Accessibility
|
Feature accessibility
|
|
|
| #Plugins
|
Plugins compatibility
|
|
|
| #Addons
|
Addons compatibility
|
|
|
| #Topsites
|
Top internet sites compatibilities
|
|
|
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
top
Developer Links
top
Other Docs
top
Developer QA Review
- Do we have automated tests for the feature?
- 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?
- 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
top
Beta1
- Will not be ready for Beta 1
- May or may not be ready for Firefox 4 final
Beta2
Beta3
Bug Tracking
top
Bug Verification
- Feature bugs that need verification
top
Bug Triage
top
Frontend
- UI changes
- Bookmarks regressions
- History regressions
Backend
- Bookmark Manager regressions
- History regressions
- Performance regressions
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
top
Smoke_Tests
top
Regression_Tests
top
Functional_Tests
top