Blocklisting/Testing: Difference between revisions

To test the full functionality of blocklist v3 against the staging server, you need to set up a Firefox profile with the following preferences:

# <code>extensions.blocklist.useMLBF.stashes</code> = true

''Note 1: During testing, the behavior should be identical regardless of whether stashes=true or stashes=false. This preference enables an optimization to save bandwidth.''<br />

''Note 2: The preferences referenced in entries 1 and 2 should be enabled by default in the latest version of Firefox and will not require manually setting them''.<br />

Blocks in v3 are managed via the admin tool on AMO, and are automatically on a schedule used to create a new bloomfilter.<br />

To set up a block entry, follow these steps:<br />

# Take note of the contents of https://kinto.stage.mozaws.net/v1/buckets/blocklists/collections/addons-bloomfilters/records<br /> ''Important Note: The new blocklist starts being generated on AMO every 6 hours (06:35 UTC), so it should be available between 06:45 – 07:00 UTC (and every 6 hours thereafter)''

# Check the contents of https://kinto.stage.mozaws.net/v1/buckets/blocklists/collections/addons-bloomfilters/records have changed since Step 8<br /> ''Note: How to verify the new stash: the stash will contain two sections - <code>blocked: []</code> and <code>unblocked: []</code>; There will be one entry for each combination or <code>"guid:version string”</code> covered by the block range set up in AMO admin. If a block is deleted, all the add-on versions should be located in the <code>stash - unblocked</code> section. Also, keep in mind that if you edit an existing block by expanding the blocked version range (i.e. you include additional add-on versions in the blocked range), you should see the new covered versions in the <code>stash - blocked</code>. Similarly, if you exclude some previous blocked versions from the block range, the excluded versions should be visible in <code>stash - unblocked</code>.''<br />

You need  to force an update of the blocklist in Firefox and verify that the add-on added in the previous step are indeed blocked. And similarly, marking an add-on as unblocked in the AMO admin tools, forcing an update and verifying that the add-on is unblocked again.<br />

To point Firefox to the stage server, follow these steps:<br />

# Go to about:addons, open the DevTools console and force an update of the blocklist by running:<br /> <code>ChromeUtils.import('resource://gre/modules/Blocklist.jsm').Blocklist.ExtensionBlocklist._client.sync()</code><br />The installed add-on should now reflect the blocked status. If the status is not automatically updated, refresh the page.

(Note: this only applies to Windows.)

   </tr>

</table>