FuncUnit NPM module

[daffl]

To follow up on the discussion if FuncUnit should be an NPM module started in #40 I propose the following:

Provide FuncUnit itself (basically this repository) as an NPM module but additionally add a funcunit command line tool which lets you

• Run tests in different browsers (PhantomJS by default) on the command line using Testee
• Initialize the default HTML page plus the library
• Provide a server that gathers and runs all your tests

For example:

funcunit run module.test.js --lib mocha

Will run the tests from module.test.js in PhantomJS using a default HTML test page with Mocha initialized (module.test.js has to be a valid Mocha test file of course) and report to the command line.

funcunit run *.test.js --lib qunit --browser firefox

Will run all .test.js files in Firefox using a default HTML test page with QUnit initialized and report to the command line.

funcunit server *.test.js --lib jasmine

Will start up a static webserver that when opened in a webbrowser will serve the default HTML page with Jasmine initialized and run all .test.js files in the current folder.

funcunit init test/index.html --lib mocha

Will write the default HTML test page with Mocha and FuncUnit to test/index.html.

[matthewp]

So is funcunit basically just sugar on top of testee? Or is it doing something differently? If it's just sugar I think it might be too much maintenance burden to be worth it.

[daffl]

Well the additional functionality is to provide a template HTML file for your tests and be able to generate and copy them.

Basically when using the FuncUnit command line tool you just write your tests and don't need to maintain a separate test HTML file or have the libraries available (but you can initialize them if you want). Plus serving it on a static webserver will enforce writing decoupled tests.

[matthewp]

Makes sense, 👍