-
-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
t.strictEqual on errors gives uninformative expected vs. actual #93
Comments
So after investigation it looks like I can fix this upstream in https://www.npmjs.org/package/object-inspect Thanks for raising the issue! I'll get on this when I get unbusy from nodeconf prep. |
Bump :) |
Fixed in 2.14.0 and fixed in object-inspect in 1.0.0 (including 100% test coverage). |
input: var test = require('tape');
test(function (t) {
var e = new TypeError('boo!');
t.strictEqual(undefined, e);
}); output:
|
<3 <3 <3 |
Hmm object-inspect is still not updated. I could swear I saw this working for a while but now it doesn't... any ideas? |
Woah, there was a 2.14.0 release that had this fixed but then it got ... removed from master? https://github.com/substack/tape/commits/2.14.0 |
E.g.
gives
whereas I would expect something like Node usually produces, i.e.
[TypeError: boo!]
.The text was updated successfully, but these errors were encountered: