Output results to console

[leobalter]

I would like to make an implementation of outputting the test results to the console when it's present in the global scope.

That would make QUnit more connected to Node environments and also to many browsers without removing the HTML output we currently have (that can still be omitted by not having a div#qunit).

It would also be great having this made after #531 with the standardized reporter interface.

[jzaefferer]

Would be nice to have a prototype for this.

[leobalter]

Now, with the detached reporter interface from #603 we can include a simple console output (maybe using TAP specs) when console is present and html is absent.

One advantage is getting rid of that test-on-node grunt task.

That would also fix most of the addressed issues on #521 and #540.

And for that I'm wondering if it's possible to make a variant build of QUnit without the jsDiff and the html reporter.

[jzaefferer]

@leobalter since you closed #627, will you look into this again as a separate module?

[leobalter]

After #627, I believe this is better if used in a separate module and probably as an extension of js-reporter. node-qunit is already doing a good job and I now suggest to reopen this only if we agree in some point to drop the html reporter to use the console as the main one, probably a 3.0 feature.

[jzaefferer]

We could add a section about node-qunit in qunitjs/qunitjs.com#85, maybe contribute some improvements.