Side by Side Diff: README.md
Issue 29720661:
Issue 6391 - Allow running the browser unit tests with Firefox (Closed)
Base URL: https://hg.adblockplus.org/adblockpluscore/
Patch Set: Review comments addressed.
Created May 18, 2018, 12:02 a.m.
| Left: | ||
| Right: |
Use n/p to move between diff chunks;
N/P to move between comments.
« no previous file with comments
|
« .hgignore ('k')
|
package.json » ('j')
|
no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')
| OLD | NEW |
|---|---|
| 1 Adblock Plus core | 1 Adblock Plus core |
| 2 ================= | 2 ================= |
| 3 | 3 |
| 4 This repository contains the generic Adblock Plus code that's shared between | 4 This repository contains the generic Adblock Plus code that's shared between |
| 5 platforms. This repository is not designed to be used directly, but instead to | 5 platforms. This repository is not designed to be used directly, but instead to |
| 6 serve as a dependency for `adblockplus`, `adblockpluschrome` and | 6 serve as a dependency for `adblockplus`, `adblockpluschrome` and |
| 7 `libadblockplus`. | 7 `libadblockplus`. |
| 8 | 8 |
| 9 Running the unit tests | 9 Running the unit tests |
| 10 ---------------------- | 10 ---------------------- |
| (...skipping 12 matching lines...) Expand all Loading... | |
| 23 ### Running specific tests | 23 ### Running specific tests |
| 24 | 24 |
| 25 You can specify specific test files or directories on the command line, e.g.: | 25 You can specify specific test files or directories on the command line, e.g.: |
| 26 `npm test test/synchronizer.js test/browser/elemHideEmulation.js`. | 26 `npm test test/synchronizer.js test/browser/elemHideEmulation.js`. |
| 27 | 27 |
| 28 ### Running the browser tests in a real browser | 28 ### Running the browser tests in a real browser |
| 29 | 29 |
| 30 The tests under `test/browser` require a browser environment. `npm test` will | 30 The tests under `test/browser` require a browser environment. `npm test` will |
| 31 run these in a headless browser, with each module being loaded in a new frame. | 31 run these in a headless browser, with each module being loaded in a new frame. |
| 32 | 32 |
| 33 The default is to run in both Chromium and Firefox. You can select which | |
| 34 runners to use by setting the BROWSER_TEST_RUNNERS environment. Possible | |
| 35 runners (separated by a ',') are, the default being "chromium,firefox": | |
| 36 | |
| 37 - "chromium_remote": Chromium 60 (using the remote interface) | |
| 38 - "chromium": Chrome 63 (using WebDriver) | |
| 39 - "firefox": Firefox 60 | |
| 40 | |
| 41 You can't set a specific version of the browser at runtime. | |
| 42 | |
| 33 Linting | 43 Linting |
| 34 ------- | 44 ------- |
| 35 | 45 |
| 36 You can lint the code using [ESLint](http://eslint.org). | 46 You can lint the code using [ESLint](http://eslint.org). |
| 37 | 47 |
| 38 eslint *.js chrome lib test | 48 eslint *.js chrome lib test |
| 39 | 49 |
| 40 You will need to set up ESLint and our configuration first, see | 50 You will need to set up ESLint and our configuration first, see |
| 41 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-conf ig-eyeo) | 51 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-conf ig-eyeo) |
| 42 for more information. | 52 for more information. |
| OLD | NEW |
« no previous file with comments
|
« .hgignore ('k')
|
package.json » ('j')
|
no next file with comments »
