mediawiki-extensions-Visual.../tests/parser/README

Work in progress. :)

Please see https://www.mediawiki.org/wiki/Future/Parser_development for some
information on how to get started with these tests and the current parser
architecture.

Install dependencies and run tests:

cd tests/parser
make test

== Running parserTests.js ==

For parserTests, you also need MediaWiki's parser test cases (parserTests.txt)
either in a phase3 checkout parallel to extensions (tried by default). You can
also specify a test case file as an argument.

The "make test" target in this directory downloads parserTests.txt and specifies
it as the test case automatically.  Of course, you may also run tests manually:

node ./parserTests.js

Several options are available for parserTests:

node ./parserTests.js --help

Enjoy!

== Running roundtrip tests ==

Round-trip tests are not yet ported to the current parser architecture. The
focus so far has been on parserTests and getting the parser architecture in
shape, but we'll get back to round-trip tests eventually.
First combination of WikiDom serializers with existing parser in tests/parser/parserTests.js. * Removed var from es in es.js to allow node.js to access it as global. Only alternative solution appears to be a node-specific 'exports' construct: http://nodejs.org/docs/v0.3.1/api/modules.html * Added es.Document.js and es.Document.Serializer.js in es/bases. Not sure if this is the desired location. * Changed es.extend to es.extendClass in the serializers * Modified the first parser test to include the WikiDom modules and call the new HTML serializer 2011-11-03 13:55:48 +00:00			`Work in progress. :)`

Update README 2011-12-13 10:03:01 +00:00			`Please see https://www.mediawiki.org/wiki/Future/Parser_development for some`
Follow-up to r106001: Fix typo spotted by Nikerabbit. Good catch! 2011-12-13 13:00:57 +00:00			`information on how to get started with these tests and the current parser`
Update README 2011-12-13 10:03:01 +00:00			`architecture.`
First combination of WikiDom serializers with existing parser in tests/parser/parserTests.js. * Removed var from es in es.js to allow node.js to access it as global. Only alternative solution appears to be a node-specific 'exports' construct: http://nodejs.org/docs/v0.3.1/api/modules.html * Added es.Document.js and es.Document.Serializer.js in es/bases. Not sure if this is the desired location. * Changed es.extend to es.extendClass in the serializers * Modified the first parser test to include the WikiDom modules and call the new HTML serializer 2011-11-03 13:55:48 +00:00
As much as I have loved writing Makefiles... I've replaced its functionality with package.json, mostly so we can avoid non-node dependencies. This is one of the recommended practices. We should consider moving tests/parser into modules/parser/tests, other node projects keep all module code in one directory. Explained in the README how to use npm to load the dependencies and run tests. Too bad about NODE_PATH... Don't try to find parserTests.txt in assorted places--if it isn't present, fetch from gerrit. You can symlink from core if you're developing on both parsers, and the fetch script will not overwrite. Use __dirname in parserTests.js to allow the script to run independent of current working directory. Change-Id: I4c8b884e91f4fdeae385c7697aff768bdd199dd5 2012-03-24 23:31:48 +00:00			`Install dependencies and run tests:`

			`cd tests/parser`
			`make test`
Update README 2011-12-13 10:03:01 +00:00
			`== Running parserTests.js ==`

			`For parserTests, you also need MediaWiki's parser test cases (parserTests.txt)`
			`either in a phase3 checkout parallel to extensions (tried by default). You can`
			`also specify a test case file as an argument.`

* Convert __patched-html-parser to .coffee. Note that the compiled .js file (generated by "make"/"make test") is still under version control so folks can work on the project even without a running "coffee" command in PATH. Also updated README to mention coffee-script and "make test". 2012-02-18 18:54:12 +00:00			`The "make test" target in this directory downloads parserTests.txt and specifies`
			`it as the test case automatically. Of course, you may also run tests manually:`
Update README 2011-12-13 10:03:01 +00:00
			`node ./parserTests.js`

			`Several options are available for parserTests:`

			`node ./parserTests.js --help`

			`Enjoy!`

			`== Running roundtrip tests ==`

			`Round-trip tests are not yet ported to the current parser architecture. The`
			`focus so far has been on parserTests and getting the parser architecture in`
			`shape, but we'll get back to round-trip tests eventually.`