Request: Fast-track npm release

[slevithan]

The QUnit 1.9.0 change log says this:

Change package.json name property to 'qunitjs' to avoid conflicht with node-qunit; will publish next release to npm

I currently use node-qunit in my XRegExp library, which will soon be ready for its 3.0.0 release. As part of this release, I would like to switch from using node-qunit to the official qunitjs. For largely selfish reasons (for myself and anyone else who might hold back project releases in order to switch to qunitjs), I'm hoping that QUnit can release the next version as soon as it's ready as an npm package (assuming this means that QUnit's qunitjs package will be usable on the command line, similar to node-qunit). Presumably, other changes related to better supporting npm and Node.js (such as #190) would also make it into the next QUnit release.

[jzaefferer]

1.9.0 is on npm, as the first release to land there. The changelog is based on commit messages.

node-qunit provides a bunch of additional features for non-browser based testing that QUnit itself likely won't ever get though.

[slevithan]

1.9.0 is on npm, as the first release to land there. The changelog is based on commit messages.

Ah, cool.

node-qunit provides a bunch of additional features for non-browser based testing that QUnit itself likely won't ever get though.

To clarify, does this mean that QUnit (the official release) does not now and has no plans to support testing on the command line via npm?

[jzaefferer]

No plans, yeah, but as usual, its open to contributions. node-qunit goes way beyond what I'd be willing to maintain here, but if we can come up with something simple, I'd land it. In general you can use QUnit in node: https://github.com/jquery/qunit/blob/master/test/node-test.js

[slevithan]

Fair 'nuff. I probably won't be the one to contribute such changes, but QUnit CLI Boilerplate by @jdalton might be a good source of inspiration.

[jzaefferer]

How about including something like that cli boilerplate as addon for QUnit, similar to the phantomjs addon?

[slevithan]

That would be most excellent. It's MIT licensed, so it should be no problem to add. Of course, it would be ideal to get buy-in from @jdalton, too. ;-) He uses QUnit CLIB with his Lo-Dash project, which also uses a number of nice extensions to QUnit's standard test runner: more readable browser names, checkbox for loading via RequireJS, and dropdown for switching between development and minified source of the library being tested.

[jdalton]

I'm in ;)

[jzaefferer]

Good! @jdalton are there features you'd like to see land upstream?

The QUnit.config.urlConfig might also be useful to simplify some stuff: http://api.qunitjs.com/QUnit.config/ (urlConfig and last example)

[Krinkle]

Also note that node-qunit is actually using the official qunit release. It adds a wapper around it for cli usage.

[jzaefferer]

Fixed in qunitjs/qunitjs.com@477af0b - I've added a link to the extensions page: http://qunitjs.com/extensions/
That way @jdalton can continue maintaining his extension, which I don't want to take over.

[jdalton]

Sweet. I can dig it ;D