If the referred test fails, I get this message:

```
>> Datetime Parse - should parse skeleton
>> Message: { skeleton: "yQQQ" }
>> Actual: null
>> Expected: "Fri Jan 01 2010 00:00:00 GMT-0800 (PST)"
>> at http://localhost:9001/external/qunit/qunit/qunit.js:593
>>   at http://localhost:9001/functional/date/parse.js:47
>>   at http://localhost:9001/external/qunit/qunit/qunit.js:203
>>   at http://localhost:9001/external/qunit/qunit/qunit.js:361
>>   at process (http://localhost:9001/external/qunit/qunit/qunit.js:1453)
>>   at http://localhost:9001/external/qunit/qunit/qunit.js:479
```

If I remove the duplicative message, I would get this:

```
>> Datetime Parse - should parse skeleton
>> Message: null
>> Actual: null
>> Expected: "Fri Jan 01 2010 00:00:00 GMT-0800 (PST)"
>> at http://localhost:9001/external/qunit/qunit/qunit.js:593
>>   at http://localhost:9001/functional/date/parse.js:47
>>   at http://localhost:9001/external/qunit/qunit/qunit.js:203
>>   at http://localhost:9001/external/qunit/qunit/qunit.js:361
>>   at process (http://localhost:9001/external/qunit/qunit/qunit.js:1453)
>>   at http://localhost:9001/external/qunit/qunit/qunit.js:479
```

The former at least gives me which skeleton failed in a quick easy first glance. The latter doesn't. Although, one will can always figure it out by looking at the stack trace and seeking the failing line in the code.

Any idea of a better message to be used instead?

By the way, if Message is `null`, couldn't QUnit simply skip it from being shown?