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 'c6e8c53f1b'
${ noResults }
pegjs/spec
History
David Majda c6e8c53f1b Expectation refactoring 2/7: Restructure "class" expectations 
Changes:

  * Remove the "value" property (it is replaced by other properties).

  * Add the "parts", "inverted", and "ignoreCase" properties (which
    allow more structured access to expectation data).
 		9 years ago
..
api Revert "Use literal raw text in error messages" 9 years ago
behavior Expectation refactoring 2/7: Restructure "class" expectations 9 years ago
unit Expectation refactoring 2/7: Restructure "class" expectations 9 years ago
vendor/jasmine Upgrade jasmine and jasmine-node 11 years ago
.eslintrc.json ESLint: Set environments better 9 years ago
README.md Use http-server to serve specs and benchmarks to the browser 9 years ago
helpers.js Rename the "PEG" variable to "peg" 9 years ago
index.html Update version to 0.9.0 9 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 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:

    $ node_modules/.bin/http-server

  5. Point your browser to the spec suite.

  6. Watch the specs pass (or fail).