SearchHijacking/TestPlan: Difference between revisions
Jump to navigation
Jump to search
Paul.silaghi (talk | contribs) (Created page with "= Search Hijacking=") |
Paul.silaghi (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= Search Hijacking= | = Search Hijacking = | ||
{| class="fullwidth-table" | |||
|- | |||
| Feature | |||
| Status | |||
| Lead Engineer | |||
| QA Lead | |||
| Status | |||
|- | |||
| Search Hijacking | |||
| {{StatusHealthy|status=Landed in Firefox 8}} | |||
| Gavin Sharp | |||
| Paul Silaghi | |||
| {{StatusHealthy|status=In progress}}<br> | |||
|} | |||
== Summary == | |||
*Web search is a lucrative business and so the search integration points in Web browsers have become a target for add-ons -- from legitimate, to grayware, to malware. The collection of techniques used to circumvent browser search defaults to funnel search revenues to third parties is referred to as "Search hijacking". | |||
*With the increase in search hijacking and it's negative effect on user choice and control, Mozilla is looking into ways to help users defend themselves. | |||
== Reference == | |||
*Design and infrastructure: | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=718088 bug 718088] - offer to re-set keyword.URL if it has a non-default value | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=724145 bug 724145] - telemetry for search hijacking | |||
== Use Cases to Test == | |||
;Basic Functional Testing | |||
;Edge Cases | |||
== Test Cases == | |||
*A list of test cases for this feature can be found here: [http://bit.ly/vE9E51 Test Cases] | |||
== Important bugs == | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=738804 bug 738804] - back out keyword.URL prompting changes | |||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=736878 bug 736878] - keyword.URL reset prompt doesn't properly re-set prefs if default engine is modified | |||
Revision as of 14:27, 27 March 2012
Search Hijacking
| Feature | Status | Lead Engineer | QA Lead | Status |
| Search Hijacking | Landed in Firefox 8 | Gavin Sharp | Paul Silaghi | In progress |
Summary
- Web search is a lucrative business and so the search integration points in Web browsers have become a target for add-ons -- from legitimate, to grayware, to malware. The collection of techniques used to circumvent browser search defaults to funnel search revenues to third parties is referred to as "Search hijacking".
- With the increase in search hijacking and it's negative effect on user choice and control, Mozilla is looking into ways to help users defend themselves.
Reference
- Design and infrastructure:
- bug 718088 - offer to re-set keyword.URL if it has a non-default value
- bug 724145 - telemetry for search hijacking
Use Cases to Test
- Basic Functional Testing
- Edge Cases
Test Cases
- A list of test cases for this feature can be found here: Test Cases
Important bugs
- bug 738804 - back out keyword.URL prompting changes
- bug 736878 - keyword.URL reset prompt doesn't properly re-set prefs if default engine is modified