Repository navigation
assert: throw real error in doesNotThrow() #12079
Description
Activity
- changed the title
[-]assert: throw error in doesNotThrow()[/-][+]assert: throw real error in doesNotThrow()[/+]on Mar 27, 2017 If it throws the passed function's error instead, then is
assert.doesNotThrow(fn)any different in effect fromfn()? (That doesn't mean we shouldn't make this change. Just trying to get clarity.)
Currently
assert.doesNotThrow()does not actually throw or otherwise give the message/content of the unexpected error. Instead it just throws a 'Got unwanted error' error, which isn't really helpful. It would be nice to either throw the seen error instead (preferred) or at the very least attach the unexpected error as a property on the thrown error.