The HTML discopane (bug 1546248) and the extension recommendations (bug 1550911) share the same internal logic for retrieving recommended extensions. Tests that mock the discovery API (by assigning the URL of a test server to `extensions.getAddons.discovery.api_url`) should ensure that only one of the two is enabled.
Bug 1557369 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The HTML discopane (bug 1546248) and the extension recommendations (bug 1550911) share the same internal logic for retrieving recommended extensions. Tests that mock the discovery API (by assigning the URL of a test server to `extensions.getAddons.discovery.api_url`) should ensure that only one of the two is enabled. Otherwise an unexpected request can be triggered from a recommended extension section when the extension list view is opened, which causes a test to fail. An example of a failing test is `browser_html_discover_view_prefs.js`. The test confirms that the discovery API isn't requested when the discovery pane is disabled. When the discopane is disabled, the next default view is the extension list. In XUL `about:addons`, there are no recommendations. However, when HTML `about:addons` is enabled, [the test](https://searchfox.org/mozilla-central/rev/153172de0c5bfca31ef861bd8fc0995f44cada6a/toolkit/mozapps/extensions/test/browser/browser_html_discover_view_prefs.js#40) fails because of an unexpected request from the recommended extension section of the list view.