Issue 6930 - Add support for Microsoft Edge to WebDriver-based test automation

README.md

 [![Pipeline status](https://gitlab.com/eyeo/adblockplus/adblockpluschrome/badges/master/build.svg)](https://gitlab.com/eyeo/adblockplus/adblockpluschrome/pipelines/)
 
 Adblock Plus for Chrome, Opera, Microsoft Edge and Firefox
 ==========================================================
 
 This repository contains the platform-specific Adblock Plus source code for
 Chrome, Opera, Microsoft Edge and Firefox. It can be used to build
 Adblock Plus for these platforms, generic Adblock Plus code will be extracted
 from other repositories automatically (see _dependencies_ file).
 
@@ skipping 86 matching lines @@
 The unit tests will run automatically once the page loads.
 
 ### External test runner
 
 There is also an external test runner that can be invoked from the
 command line in order to run the unit tests along some integration
 tests on different browsers, and automatically run the linter as well.
 
 On Windows, in order to use the test runner, in addition to setting up a Linux
 environment as outlined above, you need to have Node.js installed in your native
-Windows environment. Then run the commands below from within PowerShell or
+Windows environment.
+Also you are going to have to install [Microsoft Webdriver](https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/)

[Sebastian Noack, 2018/12/06 03:47:30]

This will be outdated very soon, as on Insider builds and future releases,
Microsoft WebDriver will be a Windows Feature on Demand.

+and ensure that it can be found on your path.
+Then run the commands below from within PowerShell or
 cmd.exe (unlike when building the extension which needs to be done from Bash).
 
+
 Make sure the required packages are installed and up-to-date:
 
     npm install
 
 Start the testing process for all browsers:
 
     npm test
 
 Start the testing process in one browser only:
 
-    npm test -- -g <Firefox|Chromium>
+    npm test -- -g <Firefox|Chromium|Edge>
 
 By default it downloads (and caches) and runs the tests against the
 oldest compatible version and the latest release version of each browser.
 In order to run the tests against a different version set the CHROMIUM_BINARY
 or FIREFOX_BINARY environment variables. Following values are accepted:
 

[geo, 2018/12/05 13:35:27]

Maybe I should mention that for Edge, we always test only against the installed
version, but I don't know exactly how to formulate that, or where to place it. 

 * `installed`
   * Uses the version installed on the system.
 * `path:<path>`
   * Uses the binary located at the given path.
 * `download:<version>`
   * Downloads the given version (for Firefox the version must be in the
     form `<major>.<minor>`, for Chromium this must be the revision number).
 
 Linting
 -------
 
 You can lint the code using [ESLint](http://eslint.org).
 
 You will need to setup first. This will install our configuration
 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-config-eyeo)
 and everything needed after you run:
 
     npm install
 
 Then you can run to lint the code:
 
     npm run lint