Publish this as a package on npm so it can be included as a dependency in other projects.

• https://github.com/jonkemp/qunit-phantomjs-runner/blob/master/runner.js#L44 can run before https://github.com/jonkemp/qunit-phantomjs-runner/blob/master/runner.js#L66
• https://github.com/jonkemp/qunit-phantomjs-runner/blob/master/runner.js#L98 can run before QUnit loads

Solution is most likely to do the following:

• disable QUnit autostart
• onload:
  • attach logger
  • manually start tests via QUnit.start()

@trentmwillis thoughts on the QUnit side? If you have a better idea for coordinating the runner + qunit boot.

Hi, @jonkemp .

It seems qunitjs npm package will be renamed to qunit, see qunitjs/qunit#1232

Can you cut a new release so that things keep working?

Provide a default timeout for phantomjs to exit after if the user doesn't provide one.

Any plans for that?

PhantomJS provides an onError callback that could be implemented to provide better insight to errors in invoked qunti html page. Right now its pretty impossible to diagnose issues that exist in PhantomJS and not within a browser using the QUnit /index.html test page.

There should be a way to pass user provided arguments along to phantomjs. Currently, any arguments other than timeout get ignored.

See jonkemp/gulp-qunit#19.