Lately, we've been doing a lot of work on the reporter interface for QUnit and I think that once we start shipping a standard TAP (or other) reporter, it'll lower the barrier to adoption of QUnit for non-browser projects (specifically thinking about Node projects).
However, I think one thing that would complement that effort and make it trivial to use QUnit in those cases would be to introduce a command-line tool similar to what Mocha provides. In particular, this tool should make running QUnit tests in Node easy without having to provide a custom script.
There are some tools currently available (such as node-qunit or even mocha-qunit-ui), but it would be great to have one backed by the project that doesn't require additional overhead from the project maintainers.
As an aside: I would also very much like to see this happen so that we can unify the testing story in the Ember community, where most developers use QUnit in the browser for applications, but Mocha in node for build tools or other things.
Lately, we've been doing a lot of work on the reporter interface for QUnit and I think that once we start shipping a standard TAP (or other) reporter, it'll lower the barrier to adoption of QUnit for non-browser projects (specifically thinking about Node projects).
However, I think one thing that would complement that effort and make it trivial to use QUnit in those cases would be to introduce a command-line tool similar to what Mocha provides. In particular, this tool should make running QUnit tests in Node easy without having to provide a custom script.
There are some tools currently available (such as node-qunit or even mocha-qunit-ui), but it would be great to have one backed by the project that doesn't require additional overhead from the project maintainers.
As an aside: I would also very much like to see this happen so that we can unify the testing story in the Ember community, where most developers use QUnit in the browser for applications, but Mocha in node for build tools or other things.