Extension Blocklisting:Testing: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(Changed app.update.timer to app.update.interval (prior was obsolete info). Did not change value, since 60 secs still seemed reasonable.) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Page to plan blocklist addition tests. General goal: make sure we do not negatively affect users with new blocklist additions. | Page to plan blocklist addition tests. General goal: make sure we do not negatively affect users with new blocklist additions. | ||
= The Blocklist File = | |||
Paths can vary based on operating system. | |||
* OSX: /Users/user/Library/Application Support/Firefox/Profiles/profile/blocklist.xml | |||
* Linux: /home/user/.mozilla/firefox/profile/blocklist.xml | |||
* Windows: %APPDATA%\Mozilla\Firefox\Profiles\profile\blocklist.xml | |||
= How to Test With a Remote Blocklist File= | = How to Test With a Remote Blocklist File= | ||
| Line 6: | Line 12: | ||
* Edit about:config: | * Edit about:config: | ||
app.update. | app.update.interval = 60 | ||
extensions.blocklist.interval = 60 | extensions.blocklist.interval = 60 | ||
app.update.lastUpdateTime.blocklist-background-update-timer (reset it) | app.update.lastUpdateTime.blocklist-background-update-timer (reset it) | ||
| Line 19: | Line 25: | ||
* Edit about:config: | * Edit about:config: | ||
app.update. | app.update.interval = 60 | ||
extensions.blocklist.interval = 60 | extensions.blocklist.interval = 60 | ||
app.update.lastUpdateTime.blocklist-background-update-timer (reset it) | app.update.lastUpdateTime.blocklist-background-update-timer (reset it) | ||
| Line 35: | Line 41: | ||
* Edit about:config: | * Edit about:config: | ||
app.update. | app.update.interval = 60 | ||
extensions.blocklist.interval = 60 | extensions.blocklist.interval = 60 | ||
extensions.blocklist.url = https://bugzilla.mozilla.org/attachment.cgi?id=301878 | extensions.blocklist.url = https://bugzilla.mozilla.org/attachment.cgi?id=301878 | ||
| Line 42: | Line 48: | ||
== Blocklisting by severities == | == Blocklisting by severities == | ||
You can blocklist the severity of the plugin or extension. To do so, edit your blocklist.xml file and add | You can blocklist the severity of the plugin or extension. To do so, edit your blocklist.xml file and add: <versionRange severity="x"/> | ||
Example: | Example: | ||
| Line 50: | Line 56: | ||
</pluginItem> | </pluginItem> | ||
Severity ratings: | * Severity ratings: | ||
** 0 = out of date | |||
** 1 = soft blocked | |||
** 2 = hard blocked | |||
** 3 = default? | |||
= Basic checks = | = Basic checks = | ||
Latest revision as of 00:47, 29 September 2011
Page to plan blocklist addition tests. General goal: make sure we do not negatively affect users with new blocklist additions.
The Blocklist File
Paths can vary based on operating system.
- OSX: /Users/user/Library/Application Support/Firefox/Profiles/profile/blocklist.xml
- Linux: /home/user/.mozilla/firefox/profile/blocklist.xml
- Windows: %APPDATA%\Mozilla\Firefox\Profiles\profile\blocklist.xml
How to Test With a Remote Blocklist File
- Install add-on, etc.
- Edit about:config:
app.update.interval = 60 extensions.blocklist.interval = 60 app.update.lastUpdateTime.blocklist-background-update-timer (reset it) extensions.blocklist.url = <url where blocklist is located>, e.g. http://morgamic.khan-vm.mozilla.org/amo/site/blocklist/1/%APP_ID%/%APP_VERSION%/
- Restart.
- In about 60s you should see the add-on in question disabled in the EM.
How to Test With a Local Blocklist File
- Install add-on, etc.
- Edit about:config:
app.update.interval = 60 extensions.blocklist.interval = 60 app.update.lastUpdateTime.blocklist-background-update-timer (reset it) extensions.blocklist.url = "" (so your locally modified blocklist.xml doesn't get overwritten when Firefox tries to update it)
- Edit the blocklist.xml file located in your profile directory, not the app. install directory (the file is downloaded into the profile directory and read from there; the file in the app. install directory is only used as a fallback if no blocklist.xml file exists in the profile directory)
- Restart.
Testing by pointing to a testfile
- This blocklist performs the following blocks:
Blocks Java and Acrobat on all platforms. Blocks QuickTime on OSX Blocks Flash 7 and Flash 9 on Windows.
- Edit about:config:
app.update.interval = 60 extensions.blocklist.interval = 60 extensions.blocklist.url = https://bugzilla.mozilla.org/attachment.cgi?id=301878
- Restart.
Blocklisting by severities
You can blocklist the severity of the plugin or extension. To do so, edit your blocklist.xml file and add: <versionRange severity="x"/>
Example: <pluginItem> <match name ="name" exp="Silverlight"/> <versionRange severity="3"/> </pluginItem>
- Severity ratings:
- 0 = out of date
- 1 = soft blocked
- 2 = hard blocked
- 3 = default?
Basic checks
- Extensions are not disabled for application versions that aren't specified
- Extensions are not disabled for versions that aren't specified
- Extensions are disabled for versions that are specified
- Extensions are disabled for application versions that are specified
IDM Testing
- Download/install
https://bugzilla.mozilla.org/show_bug.cgi?id=382356#c40 previous versions of IDM]
- See 'how to test' above. Follow the rest of the steps.
- Restart.
Repeat these steps for the following cases/assertions:
- IDM extension disabled for all Firefox clients 3.0a1 and greater, having IDM extension versions between 2.1 and 3.3
- IDM extension is not affected for
- Extension versions outside this range, any app version
- Applications less than 3.0a1, any extension version