Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

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: Lower Firefox version. Nit in the README Created Aug. 3, 2018, 4:13 p.m.
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View unified diff | Download patch
« 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') | Show Comments Hide Comments ('s')
OLDNEW
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
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 (using the remote interface)
34 and Firefox. You can select which runners to use by setting the
35 BROWSER_TEST_RUNNERS environment, the default is
36 "chromium_remote,firefox". Possible values (separated by a ',') are:
37
38 - "chromium_remote": Chromium 60 (using the remote interface)
39 - "chromium": Chrome 63 (using WebDriver)
40 - "firefox": Firefox 60 (using WebDriver)
41
42 You can not set a specific version of the browser at runtime.
43
33 Linting 44 Linting
34 ------- 45 -------
35 46
36 You can lint the code using [ESLint](http://eslint.org). 47 You can lint the code using [ESLint](http://eslint.org).
37 48
38 eslint *.js chrome lib test 49 eslint *.js chrome lib test
39 50
40 You will need to set up ESLint and our configuration first, see 51 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) 52 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-conf ig-eyeo)
42 for more information. 53 for more information.
OLDNEW
« no previous file with comments | « .hgignore ('k') | package.json » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld