t.strictEqual on errors gives uninformative expected vs. actual

[domenic]

E.g.

var e = new TypeError('boo!');
t.strictEqual(undefined, e);

gives

expected: {}
actual: undefined

whereas I would expect something like Node usually produces, i.e. [TypeError: boo!].

[ghost]

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.

[domenic]

Bump :)

[ghost]

Fixed in 2.14.0 and fixed in object-inspect in 1.0.0 (including 100% test coverage).

[ghost]

input:

var test = require('tape');

test(function (t) {
    var e = new TypeError('boo!');
    t.strictEqual(undefined, e);
});

output:

$ node x.js
TAP version 13
# (anonymous)
not ok 1 should be equal
  ---
    operator: equal
    expected: [TypeError: boo!]
    actual:   undefined
  ...
not ok 2 test exited without ending
  ---
    operator: fail
  ...

1..2
# tests 2
# pass  0
# fail  2

[domenic]

<3 <3 <3

[domenic]

Hmm object-inspect is still not updated. I could swear I saw this working for a while but now it doesn't... any ideas?

[domenic]

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