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

Unified 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.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | browsertests.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: README.md
===================================================================
--- a/README.md
+++ b/README.md
@@ -23,11 +23,11 @@ dependencies.
### Running specific tests
You can specify specific test files or directories on the command line, e.g.:
`npm test test/synchronizer.js test/browser/elemHideEmulation.html`.
### Running the browser tests in a real browser
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).
+run these in a headless browser, with each module being loaded in a new frame.
+*Note*: Currently this environment is limited to ECMAScript 5, this limitation
+should hopefully be resolved soon.
« no previous file with comments | « no previous file | browsertests.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld