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 '5a833bd982'
${ noResults }
pegjs/test/benchmark
History
Futago-za Ryuu 5a833bd982 Moved all spec and benchmark tests 
- Moved benchmark to test/benchmark
- Moved tests to test/spec
- Removed individual servers
- Implemented single test server
- Moved server assets to test/server
- Updated Gulpfile.js
- Moved tools/impact to test/impact

This commit move's nearly all code related to testing the PEG.js module into the test directory, and also ensures they run as they did before the move.
 		7 years ago
..
css Moved all spec and benchmark tests 7 years ago
json Moved all spec and benchmark tests 7 years ago
README.md Moved all spec and benchmark tests 7 years ago
benchmarks.js Moved all spec and benchmark tests 7 years ago
index.js Moved all spec and benchmark tests 7 years ago
run Moved all spec and benchmark tests 7 years ago
runner.js Moved all spec and benchmark tests 7 years ago

README.md

PEG.js Benchmark Suite

This is the PEG.js benchmark suite. It measures speed of the parsers generated by PEG.js on various inputs. Its main goal is to provide data for code generator optimizations.

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 benchmark suite:

    $ gulp benchmark

  3. Wait for results.

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 benchmark suite using a web server:

    $ benchmark/server

  4. Point your browser to the benchmark suite.

  5. Click the Run button and wait for results.