QUnit.done should provide aggregated results

[jzaefferer]

Similar to #351

Any test runner that doesn't need live updating shouldn't have to aggregate results manually.

[JamesMGreene]

How granular/verbose are you thinking we should make it?

[Krinkle]

See #405 (comment).

[jzaefferer]

@JamesMGreene @leobalter same here, pre-2.0.

[JamesMGreene]

I would again ask:

How granular/verbose are you thinking we should make it?

For example, unlike #351, I would expect that we would not include the assertions on the done event details... or would we? What would our data object look like?

Happy to implement if we can get the data details hammered out.

[jzaefferer]

Basic structure could look like this:

QUnit.on( "runEnd", function( details ) {
    details.tests.forEach(function( test ) {
        // Access test.name, test.moduleName, test.assertions
        // assertions is the same as in testDone
    });
});

[jzaefferer]

Here's a usage example that could be simplified by implementing this ticket: https://github.com/axemclion/grunt-saucelabs#test-result-details-with-qunit

[leobalter]

@jzaefferer I'll try to address this issue on #882

[leobalter]

similarly to #351, I believe this is a wontfix for now.