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

Side by Side Diff: README.md

Issue 29373596: Issue 4838 - Use nodeunit framework for integration tests running in browser (Closed) Base URL: https://hg.adblockplus.org/adblockpluscore
Patch Set: Addressed comments and added additional minor changes Created Feb. 24, 2017, 9:17 a.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 | « no previous file | browsertests.js » ('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 10 matching lines...) Expand all
21 `npm test` will run all tests in the `test` directory of the repository. 21 `npm test` will run all tests in the `test` directory of the repository.
22 22
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.html`. 26 `npm test test/synchronizer.js test/browser/elemHideEmulation.html`.
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, but you can also run them in a real one by 31 run these in a headless browser, with each module being loaded in a new frame.
32 opening 32 *Note*: Currently this environment is limited to ECMAScript 5, this limitation
33 [test/browser/elemHideEmulation.html](test/browser/elemHideEmulation.html). 33 should hopefully be resolved soon.
OLDNEW
« no previous file with comments | « no previous file | browsertests.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld