joepie91
/
pegjs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
redux
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0ed8c6f89a'
${ noResults }
pegjs/test
History
Futago-za Ryuu 55bcaa46ef Updated ESLint configuration files 
- added "root" option to main config
- moved "env.commonjs" to root
 		7 years ago
..
api Tests: Make tracing tests more specific 8 years ago
behavior Use "test" and "tests" instead of "spec" and "specs" 8 years ago
unit Tests: Require specific modules instead of the whole library 8 years ago
vendor/mocha Use "test" and "tests" instead of "spec" and "specs" 8 years ago
.eslintrc.json Updated ESLint configuration files 7 years ago
README.md Use "test" and "tests" instead of "spec" and "specs" 8 years ago
index.html Tests: s/Spec/Test/ 8 years ago
server Tests: s/Spec/Test/ 8 years ago

README.md

PEG.js Test Suite

This is the PEG.js test suite. It ensures PEG.js works correctly. All tests should always pass on all supported platforms.

Running in Node.js

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Install all PEG.js dependencies, including development ones:

    $ npm install

  2. Execute the test suite:

    $ gulp test

  3. Watch the tests pass (or fail).

Running in the Browser

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Make sure you have Node.js installed.

  2. Install all PEG.js dependencies, including development ones:

    $ npm install

  3. Serve the test suite using a web server:

    $ test/server

  4. Point your browser to the test suite.

  5. Watch the tests pass (or fail).