Ryan Doenges 6101eb184d assert: put info in err.message, not err.name ... 4716dc6 made assert.equal() and related functions work better by generating a better toString() from the expected, actual, and operator values passed to fail(). Unfortunately, this was accomplished by putting the generated message into the error's `name` property. When you passed in a custom error message, the error would put the custom error into `name` *and* `message`, resulting in helpful string representations like "AssertionError: Oh no: Oh no". This commit resolves that issue by storing the generated message in the `message` property while leaving the error's name alone and adding a regression test so that this doesn't pop back up later. Closes #5292.		2013-04-18 15:08:35 -07:00
..
addons	test: modify async native test.js to test for #4820	2013-02-21 13:14:07 -08:00
disabled	Merge remote-tracking branch 'ry/v0.8' into master	2013-02-18 10:21:08 -08:00
fixtures	test: Fix debugger repl tests	2013-02-26 16:49:17 -08:00
gc	test: use the debug build of node-weak when necessary	2012-06-13 17:58:28 -07:00
internet	DNS: Support NAPTR queries	2013-03-06 14:31:22 +04:00
message	process: separate nextTick domain logic	2013-02-27 16:37:10 -08:00
pummel	test: Pass cli flags in pummel/test-regress-GH-892	2013-03-06 11:44:29 -08:00
simple	assert: put info in err.message, not err.name	2013-04-18 15:08:35 -07:00
common.js	test: optionally set common.PORT via env variable	2013-03-02 19:09:39 +01:00