Issue 4726 - Add tests for the element hiding emulation content script

README.md

 Adblock Plus core
 =================
 
 This repository contains the generic Adblock Plus code that's shared between
 platforms. This repository is not designed to be used directly, but instead to
 serve as a dependency for `adblockplus`, `adblockpluschrome` and
 `libadblockplus`.
 
 Running the unit tests
 ----------------------
 
 ### Requirements

[kzar, 2017/01/09 08:28:42]

If switching to this syntax for the headers mind updating the existing headers
for consistency?

[Felix Dahlke, 2017/01/10 09:16:47]

Markdown only has the underlined syntax for level one and level two headers,
hence level three headers need to use the prefixed syntax. I personally much
prefer to mix them like this rather than to switch everything to prefixed. We do
it that way in lots (if not most) of our READMEs.

[kzar, 2017/01/10 11:05:33]

Well you're right the need for the different levels of headers means you need
the prefixed syntax but I don't really see the point keeping the first two
headers using the other syntax now that you're using it. Doing that looks
inconsistent and therefore kind of ugly to me. That said I don't care enough to
argue any more so I'll leave it up to you.

 
 In order to run the unit test suite you need
 [Node.js 6 or higher](https://nodejs.org/). Once Node.js is installed please run
 `npm install` in the repository directory in order to install the required
 dependencies.
 
 ### Running all tests
 
 `npm test` will run all tests in the `test` directory of the repository.
 
-### Node.js tests

[kzar, 2017/01/09 08:28:42]

I'd prefer to call these unit tests rather than Node.js tests.

[Felix Dahlke, 2017/01/10 09:16:47]

I'll rewrite this section when removing the `test-node` and `test-browser`
scripts (see
https://codereview.adblockplus.org/29367181/diff/29367382/package.json?contex...).

+### Running specific tests
 
-`npm run test-node` will only run the tests that work in a Node.js environment.
+You can specify specific test files or directories on the command line, e.g.:
+`npm test test/synchronizer.js test/browser/elemHideEmulation.html`.
 
-You can specify specific test files on the command line, e.g.
-`npm run test-node test/synchronizer.js`.
+### Running the browser tests in a real browser
 
-### Browser tests
-
-`npm run test-browser` will only run the tests that require a browser
-environment.
-
-You can run these tests in a real browser by opening `test/browser/index.html`.
+The tests under `test/browser` require a browser environment. `npm test` will
+run these in a headless browser, but you can also run them in a real one by
+opening
+[test/browser/elemHideEmulation.html](test/browser/elemHideEmulation.html).