pegjs/test
David Majda 6817f3b964 Tests: Require specific modules instead of the whole library
Requiring the whole library was a relict from the time where the tests
were exercising the browser build when run in the browser.
2016-12-16 13:21:48 +01:00
..
api Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00
behavior Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00
unit Tests: Require specific modules instead of the whole library 2016-12-16 13:21:48 +01:00
vendor/mocha Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00
.eslintrc.json Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00
index.html Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00
README.md Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00
server Use "test" and "tests" instead of "spec" and "specs" 2016-12-08 10:05:17 +01:00

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).