Extension Blocklisting:Testing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add instructions for how to test when modifying blocklist.xml locally)
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.


= How to Test =
= How to Test With a Remote Blocklist File=
* Install extension, etc.
* Install add-on, etc.


* Edit firefox.js:
* Edit about:config:
   
   
pref("extensions.blocklist.url", "http://morgamic.khan-vm.mozilla.org/amo/site/blocklist/1/%APP_ID%/%APP_VERSION%/");
* Edit about:config:
  app.update.timer = 60
  app.update.timer = 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)
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.
* Restart.


* In about 60s you should see the add-on in question disabled in the EM.
* 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:
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.


= Basic checks =
= Basic checks =

Revision as of 20:49, 10 June 2008

Page to plan blocklist addition tests. General goal: make sure we do not negatively affect users with new blocklist additions.

How to Test With a Remote Blocklist File

  • Install add-on, etc.
  • Edit about:config:
app.update.timer = 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:
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.

Basic checks

  1. Extensions are not disabled for application versions that aren't specified
  2. Extensions are not disabled for versions that aren't specified
  3. Extensions are disabled for versions that are specified
  4. 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:

  1. IDM extension disabled for all Firefox clients 3.0a1 and greater, having IDM extension versions between 2.1 and 3.3
  2. IDM extension is not affected for
    1. Extension versions outside this range, any app version
    2. Applications less than 3.0a1, any extension version
Retrieved from "https://wiki.mozilla.org/index.php?title=Extension_Blocklisting:Testing&oldid=96238"