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 '5ce5f7a612'
${ noResults }
pegjs/spec
History
David Majda 5ce5f7a612 Specs cleanup: Use raw node types in |generateBytecode| specs 
Use raw node types instead of humanized node names in |generateBytecode|
specs. This corresponds more closely to the level the specs are written
at.
 		11 years ago
..
api Specs cleanup: Implement generated parser API specs 11 years ago
unit Specs cleanup: Use raw node types in |generateBytecode| specs 11 years ago
vendor/jasmine Upgrade jasmine and jasmine-node 11 years ago
README.md Use sentence case consistently in {spec,benchmark}/README.md headers 11 years ago
helpers.js Specs cleanup: Split specs into unit and API specs 11 years ago
index.html Specs cleanup: Implement generated parser API specs 11 years ago

README.md

PEG.js Spec Suite

This is the PEG.js spec suite. It ensures PEG.js works correctly. All specs 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 spec suite:

    $ make spec

  3. Watch the specs 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 and Python installed.

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

    $ npm install

  3. Build browser version of PEG.js:

    $ make browser

  4. Serve PEG.js root directory using a web server:

    $ python -m SimpleHTTPServer

  5. Point your browser to the spec suite.

  6. Watch the specs pass (or fail).