Firefox/Projects/Network Error Pages/Test Plan: Difference between revisions

Firefox/Projects/Network Error Pages/Test Plan (view source)

Revision as of 01:54, 25 June 2010

1,514 bytes added , 25 June 2010

→‎Automated Tests Details

Ashughes

Confirmed users

14,525

edits

@@ Line 320: / Line 320: @@
 = [[#Feature_Tests|Feature Tests Details]] =
 == [[#Automated_Tests|Automated Tests Details]] ==
+'''NOTE: Most of these may be best served as an automated and manual test'''
+* If a 404 error page meets the constraint it should be overridden.
+* If a 404 error page does not meet the constraint, it should *not* be overridden.
+* Make sure Suggestion appears when there is a very close match.
+* Make sure Suggestion does not appear when there is not remotely close match.
+* Verify that the URL is well-formed, and that the anchor element displaying it works.
+* Make sure Search appears for 404 error overrides.
+* Make sure Search does *not* appear for DNS Not Found errors.
+* Verify that the search box is pre-populated when it appears, and verify that the button actually triggers the search.
+* Verify that the search uses the user's preferred search engine when it makes sense (e.g. Google or Yahoo, but not Wikipedia).
+* Verify that the search is actually constrained to the site.
+* Make sure that Global Websearch appears both for 404 error overrides and DNS Not Found errors.
+* Make sure that the Global Websearch search box is pre-populated with search terms, and verify that the button actually triggers the search.
+* Make sure the Global Websearch search uses the user's preferred search engine when it makes sense (e.g. Google or Yahoo, but not Wikipedia).
+* Verify that the UI control (button, link, etc.) appears in the original error page, and verify that it works.
+* [Manual Error Page] Trigger a conventional 404 page that will not be overridden (just too large, etc.).  Verify that the UI control (button, link, etc.) is visible in the browser chrome, and verify that it will show the 404-override page.
+* Do the error pages validate? (I don't know if this is critical, but if we can automate it, it won't hurt to test.)
 === Developer Tests ===
@@ Line 327: / Line 344: @@
 === 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