Network Error Pages
- Development Status: - UNKNOWN (6/24/2010)
- Feature Testing: - STALLED (6/24/2010)
- Team: cbartley (dev), ashughes (qa)
- Tracking Bugs: bug 482874
Feature Description
When a requested web page cannot be loaded, Firefox should display an error page that not only describes the problem, but which also presents the user with tools to resolve the issue. It also makes sense to extend this functionality to webserver 404 (File not found) responses as well.
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
|
| 404 Pages
|
Page not found error page
|
Developer Tests, QA Tests, Beta tester coverage
|
|
| Suggestions
|
Alternate site suggestions
|
Developer Tests, QA Tests, Beta tester coverage
|
|
| Search
|
Pre-populate site-search box & button, primarily used on 404 error pages, terms derived from URL
|
Developer Tests, QA Tests, Beta tester coverage
|
|
| #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
top
Developer Links
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
- Not sure of status for ANY Firefox 4 iteration
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 482874
|
Top-level tracking bug
|
top
Bug Verification
- Feature bugs that need verification
top
Bug Triage
top
404 Pages
- Override 404 pages containing less than 250 characters served by Apache (minimizes chances of overriding custom error pages)
- Do not override 404 pages containing greater than 250 characters
- Ability to view the original 404 error page
- Ability to view the Firefox 404 override page manually when it did not automatically override
- Do the error pages validate?
- Is the spelling/grammar correct?
- Is the spelling/grammar correct for localizations?
- Does the layout look decent?
top
Search
- Pre-populate site-search box & button, primarily used on 404 error pages, terms derived from URL
- Appears for 404 error overrides
- Does not appear for DNS Not Found errors
- Search box is pre-populated when it appears
- Clicking the search button triggers a search
- Use the user's preferred search engine if it makes sense to do so
- Google, Yahoo, MSN make sense
- Wikipedia, Amazon, Ebay do not
- Global Web Search
- Similar to Search but this works for both 404 and DNS error pages, search terms derived from URL.
top
Suggestions
- Alternate URLs i.e. "Did you mean...", drawn from Places DB using "edit distance" criteria, only appears if match is pretty close
- Appear when there is a very close match
- Does not appear when there is not a close match
- Suggested URLs are well-formed
- Suggested URLs work
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