delta/node.git/lib/assert.js, branch move-debugger-tests

assert: indicate if exception message is generated

2013-10-11T17:15:03+00:00

AssertionError.generatedMessage is now true when
AssertionError.message was generated from expected and actual

Fixes #5836, #6206

src: Replace macros with util functions

2013-08-01T22:08:01+00:00

assert: replace !!!value with just !value

2013-07-30T11:29:20+00:00

Not harmful, just code cleanup.

Fixes #5885.

lib: macro-ify type checks

2013-07-24T19:49:35+00:00

Increases the grep factor. Makes it easier to harmonize type checks
across the code base.

lint

2013-04-19T23:25:11+00:00

assert: put info in err.message, not err.name

2013-04-18T22:08:35+00:00

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.

assert: Simplify AssertError creation

2013-04-03T16:52:56+00:00

assert: improve support for new execution contexts

2012-12-29T19:19:14+00:00

More detailed information in GH-693

doc: update assert.doesNotThrow() docs

2012-08-29T00:36:22+00:00

It takes an optional "expected exception" argument that is not used meaningfully
but is nevertheless documented. Undocument it, it confuses casual readers of the
documentation.

Fixes #3935.

assert: fix throws() throws an error without message property

2012-07-29T10:48:16+00:00

Fixes #2893.