pegjs

History

David Majda 747cb8afaa Reset parser position when action returns \|null\| The change does not change the benchmark suite execution speed statistically significantly. Detailed results (benchmark suite totals as reported by "jake benchmark" on Node.js 0.4.8): ----------------------------------- Test # Before After ----------------------------------- 1 128.20 kB/s 128.03 kB/s 2 130.36 kB/s 128.73 kB/s 3 126.53 kB/s 129.72 kB/s 4 127.46 kB/s 127.48 kB/s 5 127.63 kB/s 128.53 kB/s ----------------------------------- Average 128.04 kB/s 125.50 kB/s ----------------------------------- Closes GH-25.		2011-08-20 17:59:12 +02:00
..
vendor/qunit	Upgrade QUnit to the current master (c532d183664118fc2ca1)	2011-01-25 14:54:38 +01:00
checks-test.js	Do not pass \|global\| into wrapping functions in tests, it's useless	2011-02-13 12:22:56 +01:00
compiler-test.js	Reset parser position when action returns \|null\|	2011-08-20 17:59:12 +02:00
helpers.js	Add ability to start parsing from any grammar rule	2011-03-29 15:40:34 +02:00
index.html	Move test helper into its own file + reorder test file includes	2010-08-21 15:34:56 +02:00
parser-test.js	Do not pass \|global\| into wrapping functions in tests, it's useless	2011-02-13 12:22:56 +01:00
passes-test.js	Do not pass \|global\| into wrapping functions in tests, it's useless	2011-02-13 12:22:56 +01:00
README	Add command-line runner for the test suite	2011-01-25 16:59:32 +01:00
run	Test and benchmark command-line runners can be run from any directory	2011-01-26 16:08:03 +01:00

README

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 a browser
--------------------

  1. Open the index.html file in your browser.

  2. Watch the test pass (or fail).

Running from a command-line
---------------------------

  1. Make sure you have Node.js installed.

  2. Run the following command:

       ./run

  3. Watch the tests pass (or fail).