AwesomebarSearchProviderReset/TestPlan

Awesomebar Search Provider Reset

Feature	Status	Release Target	Lead engineer	QA Lead	QA Status
Awesomebar Search Provider Reset	Landed	Firefox 19	Gavin Sharp	Manuela Muntean	Signed Off

Summary

Users falling victim to "search hijacking" (keyword.URL being taken over by an unwanted search engine) is a common problem.

There are two cases we can detect:

• pref is changed, and the hostname is different (e.g. switched from the default of Google to SuperAwesomeWebDealsSearch.com)
• pref is changed, and only parameters are different (e.g. user customized to a specific type of Google search, or referral codes where added)

In either case, we could prompt the user and offer to reset the keyword.URL value to the default after they trigger a search from the location bar.

• Screenshot of notification

Reference

• bug 718088 - offer to re-set keyword.URL if it has a non-default value - RESOLVED FIXED

Use Cases to Test

Test that the notification which prompts the user is displayed when

• manually changing keyword.URL pref from "about:config", and then actually performing a keyword search
• installing an add-on that automatically changes the keyword.URL pref, and then actually performing a keyword search

Test Cases

• Test cases and test results can be seen in the Google Spreadsheet
• They are also present in MozTrap, in the Awesomebar Search Provider Reset test suite.

Bugs

• bug 732671 - Prevent third party apps to change default search engine - RESOLVED DUPLICATE
• bug 784189 - Offer to re-set keyword.URL if it has a non-default value until a better solution can be found - RESOLVED DUPLICATE
• bug 736878 - keyword.URL reset prompt doesn't properly re-set prefs if default engine is modified - RESOLVED FIXED
• bug 744957 - Enhancements to help mitigate search hijacking - RESOLVED INCOMPLETE
• bug 838864 -

Sign off

Criteria

• All the test cases were executed.
• All the blocker, critical, major bugs have been fixed.

Firefox 19 beta 5 - 2013-02-07

• bug 839410 - Notification appearing after setting keyword.URL to "http://www.google.com" or "http://www.search.google.com"
• bug 839416 - Notification doesn't appear after setting keyword.URL to something without "http://" or with an invalid URL
• Regarding the following add-ons installation: