`assert.throwsError` not recognizing thrown error

[classroomtechtools]

`assert.throwsError` not recognizing thrown error

[brainysmurf]

Hmmm. Not able to reproduce. I ran the same code in the IDE and got the expected result:

true
A unit test
✔ will fail with a bad structure

[bennettscience]

Weird. Here's my stack trace. Using v4 of the published library.

A unit test
	✘ will fail with a bad structure -> Error: Comment: 
	 ---> Error message: Expected thrown error to be of type Error
    
    at new UtgsUnit.Failure (Bundle:566:9)
    at Object.UtgsUnit.assert (Bundle:533:11)
    at Function.throws (Bundle:1112:16)
    at Function.throwsError (Bundle:1153:27)
    at ContextManager.with (Bundle:143:21)
    at Function.it (Bundle:1267:13)
    at it (Bundle:1300:23)
    at ContextManager.with (Bundle:143:21)
    at Function.describe (Bundle:1239:13)
    at describe (Bundle:1297:23)

[brainysmurf]

Okay, I think I may know what's happening. Say a library or your main project creates an error object, but another library (utgs) checks to see if it's an instance of it, it'll be false because of a kind of a huge boundary between the two.

I've seen this happen in another context, the fix was to provide the library with the class variable itself.

I've sent an email giving you ability to set library version to head, can you please see if the following code now passes?:

assert.throwsError(comment, function () {
   new MyClass(...);
}, {instanceOf: Error});

[bennettscience]

Ah, that makes sense.

Switching to HEAD works with that snippet.

[brainysmurf]

Awesome, I'll update the api to use that method instead.