AwesomebarSearchProviderReset/TestPlan: Difference between revisions
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
== Reference == | == Reference == | ||
*{{Bug|718088}} - offer to re-set keyword.URL if it has a non-default value - '''RESOLVED FIXED''' | |||
== Use Cases to Test == | == Use Cases to Test == | ||
Line 29: | Line 30: | ||
==Bugs == | ==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''' | |||
== Sign off Criteria == | == Sign off Criteria == |
Revision as of 16:08, 7 January 2013
Awesomebar Search Provider Reset
Feature | Status | Lead engineer | QA Lead |
Awesomebar Search Provider Reset | In Planning | Gavin Sharp | Manuela Muntean |
Summary
Reference
- bug 718088 - offer to re-set keyword.URL if it has a non-default value - RESOLVED FIXED
Use Cases to Test
Edge Cases
Test Cases
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