* refactor `ok` to `truthy` and `notOk` to `falsy`
* update tests to be more explicit
* update docs to use a better assertion api
* realign power-assert output
* quick typo fix
* update assertions
* convert-source-map@^1.2.0
The generateMapFileComment() method used in #662 isn't available in v1.1.2.
* use already required convert-source-map dependency
No need to require the generateMapFileComment() method separately.
Also remove unnecessary linebreak at the end of the file.
The child process is no longer killed from the main process, instead it exits
upon receiving an 'exit' message. This makes the changes from
<https://github.com/sindresorhus/ava/pull/155> redundant.
npmjs.com does not correctly display the gitter badge. My guess is that it's due to the unencoded space character in the image URL (won't know for sure until we publish again).
When loading the test file, test workers intercept the require call and load the
cached code instead. Libraries like nyc may also be intercepting require calls,
however they won't know that different code was loaded. They may then attempt to
resolve a source map from the original file location.
This commit adds a source map file comment to the cached code. The file path is
relative from the directory of the original file to where the source map is
cached.
Add a test which mimics how nyc resolves the source map.
clean-yaml-object is the error serialization tool used by node-tap.
It has some nice benefits over serailze-error including better stringification of functions and buffers.
More importantly, the shared code will help keep our tap output consistent with that of node-tap.
PR #576 changed the `t.throws()` assertion to return the thrown error, or if
asynchronous a promise for the rejection reason. Unfortunately this only worked
for asynchronous errors.
The tests cover the changes in `lib/assert.js` but `t.throws()` is an *enhanced*
assertion. This commit ensures any values returned from `lib/assert.js`
assertions are indeed returned by the corresponding `t.` assertions.