Example test for assert.throws fails about api.qunitjs.com HOT 5 CLOSED

I think this may just be a bad example. CustomError should inherit from Error, but it doesn't.

from api.qunitjs.com.

On QUnit v1.14.0 it fails with a TypeError indeed (the case of "expected" being an object is handled, but only by accident). With the latest pre build from GitHub, it fails even worse.

Expected:   
{
  "message": "some error description",
  "message": "some error description",
  "toString": function( ){
    [code]
  }
}
Source:     
    at Object.QUnit.assert.Assert.throws (https://code.jquery.com/qunit/qunit-git.js:1139:9)

It falls straight through all the different if conditions with no useful error. I think this is a valid bug. There is no reason why the object needs to be an instance of Error. The assert.throws signature would't become ambiguous. And it would support asserting thrown plain objects, which is neat.

Filed qunitjs/qunit#609.

from api.qunitjs.com.

Either the docu or the API has to change.
Which way will we go?

from api.qunitjs.com.

The API is about to be fixed on qunitjs/qunit#610, @Legends. We're going to keep this issue open until we land that.

from api.qunitjs.com.

Fixed by @Krinkle in the current codebase (will be released in v1.15).

from api.qunitjs.com.