SearchHijacking/TestPlan: Difference between revisions
Jump to navigation
Jump to search
Paul.silaghi (talk | contribs) No edit summary |
Paul.silaghi (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 10: | Line 10: | ||
|- | |- | ||
| Search Hijacking | | Search Hijacking | ||
| {{StatusHealthy|status= | | {{StatusHealthy|status=OK}} | ||
| Gavin Sharp | | Gavin Sharp | ||
| Paul Silaghi | | Paul Silaghi | ||
| Line 39: | Line 39: | ||
== Test Cases == | == Test Cases == | ||
*A list of test cases for this feature can be found here: [http://bit.ly/ | *A list of test cases for this feature can be found here: [http://bit.ly/HaT8Il Test Cases] | ||
== Important bugs == | == Important bugs == | ||
Latest revision as of 14:31, 27 March 2012
Search Hijacking
| Feature | Status | Lead Engineer | QA Lead | Status |
| Search Hijacking | OK | 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