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 '73de2c9384'
${ noResults }
pegjs/spec
History
David Majda 73de2c9384 Switch from Jasmine to Mocha & Chai 
The switch is mostly mechanical, with assertions translated 1:1. The
biggest non-mechanical part is rewriting Jasmine custom matchers as Chai
helpers. The matchers were streamlined and simplified in the process and
their messages were made more in line with messages produced by built-in
Chai helpers.

Fixes #409.
 		7 years ago
..
api Switch from Jasmine to Mocha & Chai 7 years ago
behavior Switch from Jasmine to Mocha & Chai 7 years ago
unit Switch from Jasmine to Mocha & Chai 7 years ago
vendor/mocha Switch from Jasmine to Mocha & Chai 7 years ago
.eslintrc.json Switch from Jasmine to Mocha & Chai 7 years ago
README.md Switch from Make to Gulp 8 years ago
index.html Switch from Jasmine to Mocha & Chai 7 years ago
server Code style: Remove unnecessary "eslint-disable" directives 8 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:

    $ gulp 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. Serve the spec suite using a web server:

    $ spec/server

  4. Point your browser to the spec suite.

  5. Watch the specs pass (or fail).