Issue 4495 - Update adblockplustests dependency

metadata.common

 [general]
 version = 1.12.2
 backgroundScripts = lib/polyfills/url.js
   lib/polyfills/promise.js
   lib/polyfills/fetch.js
   ext/common.js
   ext/background.js
   lib/compat.js
   lib/info.js
   lib/publicSuffixList.js
   lib/adblockplus.js
   messageResponder.js
   background.js
 testScripts = ../ext/common.js
   ../ext/background.js
   ../lib/compat.js
   ../lib/info.js
   ../lib/adblockplus.js
   ../lib/publicSuffixList.js
   common.js
-  tests/adblockplus.js
+  tests/prefs.js
   tests/versionComparator.js
   tests/url.js
   tests/cssEscaping.js
 permissions = http://*/* https://*/*
 author = Eyeo GmbH
 
 [contentScripts]
 document_start = ext/common.js ext/content.js cssProperties.js include.preload.js
 document_end = include.postload.js
 
@@ skipping 19 matching lines @@
 skin/features/malware.png = adblockplusui/skin/features/malware.png
 skin/features/social.png = adblockplusui/skin/features/social.png
 skin/features/tracking.png = adblockplusui/skin/features/tracking.png
 skin/fonts/CreteRound-Italic.otf = adblockplusui/skin/fonts/CreteRound-Italic.otf
 skin/fonts/CreteRound-Regular.otf = adblockplusui/skin/fonts/CreteRound-Regular.otf
 skin/social/facebook.png = adblockplusui/skin/social/facebook.png
 skin/social/googleplus.png = adblockplusui/skin/social/googleplus.png
 skin/social/renren.png = adblockplusui/skin/social/renren.png
 skin/social/twitter.png = adblockplusui/skin/social/twitter.png
 skin/social/weibo.png = adblockplusui/skin/social/weibo.png
-qunit/qunit.js = adblockplustests/chrome/content/qunit.js
-qunit/qunit.css = adblockplustests/chrome/content/qunit.css
 
 [convert_js]
 lib/adblockplus.js =
   lib/filterComposer.js
   lib/filterValidation.js
   lib/icon.js
   lib/io.js
   lib/messaging.js
   lib/notificationHelper.js
   lib/prefs.js
@@ skipping 23 matching lines @@
   adblockpluscore/lib/subscriptionClasses.js
   adblockpluscore/lib/synchronizer.js
 lib/adblockplus.js[module] = true
 lib/adblockplus.js[source_repo] = https://hg.adblockplus.org/adblockpluscore/
 lib/adblockplus.js[autoload] = filterListener,synchronizer,requestBlocker,popupBlocker,contentBlocking,subscriptionInit,filterComposer,stats,uninstall
 ext/common.js = ext/common.js
 ext/background.js = ext/background.js
 ext/background.js[brace_style] = expand
 include.postload.js = subscriptionLink.postload.js composer.postload.js
 
-qunit/tests/adblockplus.js = adblockplustests/chrome/content/tests/domainRestrictions.js
-  adblockplustests/chrome/content/tests/filterClasses.js

[Sebastian Noack, 2016/10/06 11:47:36]

Do I miss something here, or shouldn't we import those tests from
adblockpluscore instead in order to run them on Chrome?

[Wladimir Palant, 2016/10/06 12:09:29]

This makes little sense. In adblockpluscore these tests run in a sandbox, making
them run in Chrome against the real extension would require considerable effort.
And effectively we would only be testing JSHydra which is expected to go away
soon.

[Sebastian Noack, 2016/10/06 12:24:17]

Not sure about the effort, but I think it generally makes sense to run these
tests on the actual platform, the code is used on. One could argue that nodejs
is the same platform, but that's not quite true. Though nodejs is using the same
JavaScript engine, chances are that your nodejs version is using a different V8
version than the latest Chrome, not to mention that the global namespace is for
the most part quite different in nodejs from what you have in the browser. Also
what is about platforms like Microsoft Edge that don't even use V8? Do you
remember, when a misoptimization by JavaScriptCore (WebKit) of our element
hiding code caused each page to be rendered blank?

[Wladimir Palant, 2016/10/06 14:27:58]

I don't really remember that misoptimization being caught by unit tests, I think
it was manual testing?

Either way, these are *unit* tests, their purpose it to test *our* code and
making sure that it is correct. The only platform relevant here is ECMAScript 6.
Catching errors in the ECMAScript implementation cannot be the purpose - we
cannot possibly know what to test.

Globals are different, you are right. But these are integration points and
should be subject to integration tests if necessary - making sure that the
platform behaves the way we expect it to. Luckily, the unit tests now show
clearly what globals they depend on
(https://hg.adblockplus.org/adblockpluscore/file/cc214664f060/test/_common.js#l35)
so we can add integration tests if we have concerns. The only non-trivial thing
in there is the version comparator and that one is already tested in Chrome.

[Sebastian Noack, 2016/10/06 16:24:23]

I don't agree, but if we still want to run the core tests on Chrome and Edge
this is apparently a separate effort, unrelated of this change. So LGTM.

-  adblockplustests/chrome/content/tests/filterNotifier.js
-  adblockplustests/chrome/content/tests/filterStorage.js
-  adblockplustests/chrome/content/tests/matcher.js
-  adblockplustests/chrome/content/tests/prefs.js
-  adblockplustests/chrome/content/tests/regexpFilters_matching.js
-  adblockplustests/chrome/content/tests/subscriptionClasses.js
-qunit/tests/adblockplus.js[source_repo] = https://hg.adblockplus.org/adblockplustests/
-
 [import_locales]
 adblockplus/chrome/locale/*/global.properties = subscription_invalid_location
   remove_subscription_warning
   notification_antiadblock_title
   notification_antiadblock_message
   filter_unknown_option
   filter_invalid_regexp
   filter_elemhide_duplicate_id
   filter_elemhide_nocriteria
   filter_cssproperty_nodomain
@@ skipping 13 matching lines @@
   addSubscription.label
   addSubscriptionAdd.label
   addSubscriptionOther.label
   acceptableAds2.label
   viewList.label
   readMore.label
 adblockplus/chrome/locale/*/subscriptionSelection.dtd = location.label
   title.label
 adblockplus/chrome/locale/*/meta.properties = =name
 adblockplusui/locale/*/firstRun.json = =*