Action Based on Update.xml After Update
- Development Status: - COMPLETE, pending AUS changes (6/24/2010)
- Feature Testing: - WAITING (6/24/2010)
- Team: rs (dev), ashughes (qa)
- Tracking Bugs: bug 538331, bug 549969, bug 459972
Feature Description
Instead of just opening a web page after an update Firefox should be able to perform an action based upon the update's metadata. For example, after an update the user can be presented with a notification asking them to join the Firefox Facebook group along with the ability to navigate to the Firefox Facebook group.
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone.
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.
Test Item
|
Description
|
Covered By
|
Status
|
#Update_Actions
|
Different actions after update and UI changes
|
Developer Tests, QA Litmus Tests, QA Mozmill Tests
|
Pending Server-side changes
|
#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
|
#Security
|
Security concerns
|
|
pending-feedback
|
top
Item
|
Description
|
Status
|
#Developer_Tests
|
Links to automated developer tests
|
pending-feedback
|
#Mozmill_Tests
|
Links to automated mozmill feature test cases
|
none
|
top
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
|
top
Project Wiki
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
- 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
- Not ready
- Client-side frontend and backend changes have landed and are ready
- Waiting on Server-side (AUS) changes
Beta2
Beta3
Bug Tracking
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
Security
- Details of security test requirements
top
Developer Tests
- Links to automated developer tests
top
Mozmill Tests
top
Smoke_Tests
top
Regression_Tests
top
Functional_Tests
top
Testdays
Bugdays
Meetups