ava 0.16.0 → 0.18.2

package/readme.md

@@ -2,7 +2,7 @@
 
 > Futuristic test runner
 
-[![Build Status: Linux](https://travis-ci.org/avajs/ava.svg?branch=master)](https://travis-ci.org/avajs/ava) [![Build status: Windows](https://ci.appveyor.com/api/projects/status/e7v91mu2m5x48ehx/branch/master?svg=true)](https://ci.appveyor.com/project/ava/ava/branch/master) [![Coverage Status](https://coveralls.io/repos/github/avajs/ava/badge.svg?branch=master)](https://coveralls.io/github/avajs/ava?branch=master) [![Dependency Status](https://dependencyci.com/github/avajs/ava/badge)](https://dependencyci.com/github/avajs/ava) [![Gitter](https://badges.gitter.im/join_chat.svg)](https://gitter.im/avajs/ava)
+[![Build Status: Linux](https://travis-ci.org/avajs/ava.svg?branch=master)](https://travis-ci.org/avajs/ava) [![Build status: Windows](https://ci.appveyor.com/api/projects/status/e7v91mu2m5x48ehx/branch/master?svg=true)](https://ci.appveyor.com/project/ava/ava/branch/master) [![Coverage Status](https://coveralls.io/repos/github/avajs/ava/badge.svg?branch=master)](https://coveralls.io/github/avajs/ava?branch=master) [![Dependency Status](https://dependencyci.com/github/avajs/ava/badge)](https://dependencyci.com/github/avajs/ava) [![XO code style](https://img.shields.io/badge/code_style-XO-5ed9c7.svg)](https://github.com/sindresorhus/xo) [![Gitter](https://badges.gitter.im/join_chat.svg)](https://gitter.im/avajs/ava)
 
 Even though JavaScript is single-threaded, IO in Node.js can happen in parallel due to its async nature. AVA takes advantage of this and runs your tests concurrently, which is especially beneficial for IO heavy tests. In addition, test files are run in parallel as separate processes, giving you even better performance and an isolated environment for each test file. [Switching](https://github.com/sindresorhus/pageres/commit/663be15acb3dd2eb0f71b1956ef28c2cd3fdeed0) from Mocha to AVA in Pageres brought the test time down from 31 sec to 11 sec. Having tests run concurrently forces you to write atomic tests, meaning tests don't depend on global state or the state of other tests, which is a great thing!
 
@@ -14,15 +14,18 @@ Follow the [AVA Twitter account](https://twitter.com/ava__js) for updates.
 
 Translations: [Español](https://github.com/avajs/ava-docs/blob/master/es_ES/readme.md), [Français](https://github.com/avajs/ava-docs/blob/master/fr_FR/readme.md), [Italiano](https://github.com/avajs/ava-docs/blob/master/it_IT/readme.md), [日本語](https://github.com/avajs/ava-docs/blob/master/ja_JP/readme.md), [한국어](https://github.com/avajs/ava-docs/blob/master/ko_KR/readme.md), [Português](https://github.com/avajs/ava-docs/blob/master/pt_BR/readme.md), [Русский](https://github.com/avajs/ava-docs/blob/master/ru_RU/readme.md), [简体中文](https://github.com/avajs/ava-docs/blob/master/zh_CN/readme.md)
 
+
 ## Contents
 
 - [Usage](#usage)
 - [CLI Usage](#cli)
+- [Debugging](#debugging)
 - [Reporters](#reporters)
 - [Configuration](#configuration)
 - [Documentation](#documentation)
 - [API](#api)
 - [Assertions](#assertions)
+- [Snapshot testing](#snapshot-testing)
 - [Tips](#tips)
 - [FAQ](#faq)
 - [Recipes](#recipes)
@@ -31,6 +34,7 @@ Translations: [Español](https://github.com/avajs/ava-docs/blob/master/es_ES/rea
 - [Links](#links)
 - [Team](#team)
 
+
 ## Why AVA?
 
 - Minimal and fast
@@ -38,15 +42,18 @@ Translations: [Español](https://github.com/avajs/ava-docs/blob/master/es_ES/rea
 - Runs tests concurrently
 - Enforces writing atomic tests
 - No implicit globals
+- Includes TypeScript & Flow type definitions
+- [Magic assert](#magic-assert)
 - [Isolated environment for each test file](#process-isolation)
-- [Write your tests in ES2015](#es2015-support)
+- [Write your tests in ES2017](#es2017-support)
 - [Promise support](#promise-support)
 - [Generator function support](#generator-function-support)
 - [Async function support](#async-function-support)
 - [Observable support](#observable-support)
 - [Enhanced assertion messages](#enhanced-assertion-messages)
 - [TAP reporter](#tap-reporter)
-- [Clean stack traces](#clean-stack-traces)
+- [Automatic migration from other test runners](https://github.com/avajs/ava-codemods#migrating-to-ava)
+
 
 ## Test syntax
 
@@ -62,7 +69,15 @@ test(t => {
 
 ### Add AVA to your project
 
-Install AVA globally and run it with `--init` to add AVA to your `package.json`:
+Install AVA globally and run it with `--init` to add AVA to your `package.json`. [Yarn](https://yarnpkg.com/) currently provides significant speed improvements over npm during the installation process. Consider [using Yarn](https://yarnpkg.com/en/docs/install) if the installation is too slow for your needs.
+
+
+```console
+$ yarn global add ava
+$ ava --init
+```
+
+If you prefer using npm:
 
 ```console
 $ npm install --global ava
@@ -78,7 +93,7 @@ Your `package.json` will then look like this:
     "test": "ava"
   },
   "devDependencies": {
-    "ava": "^0.15.0"
+    "ava": "^0.18.0"
   }
 }
 ```
@@ -89,12 +104,17 @@ Any arguments passed after `--init` are added as config to `package.json`.
 
 You can also install AVA directly:
 
+```console
+$ yarn add --dev ava
+```
+
+Alternatively using npm:
+
 ```console
 $ npm install --save-dev ava
 ```
 
-You'll have to configure the `test` script in your `package.json` to use `ava`
-(see above).
+You'll have to configure the `test` script in your `package.json` to use `ava` (see above).
 
 ### Create your test file
 
@@ -114,8 +134,6 @@ test('bar', async t => {
 });
 ```
 
-<img src="media/screenshot.png" width="150" align="right">
-
 ### Run it
 
 ```console
@@ -139,18 +157,19 @@ $ ava --help
     ava [<file|directory|glob> ...]
 
   Options
-    --init             Add AVA to your project
-    --fail-fast        Stop after first test failure
-    --serial, -s       Run tests serially
-    --require, -r      Module to preload (Can be repeated)
-    --tap, -t          Generate TAP output
-    --verbose, -v      Enable verbose output
-    --no-cache         Disable the transpiler cache
-    --match, -m        Only run tests with matching title (Can be repeated)
-    --watch, -w        Re-run tests when tests and source files change
-    --source, -S       Pattern to match source files so tests can be re-run (Can be repeated)
-    --timeout, -T      Set global timeout
-    --concurrency, -c  Maximum number of test files running at the same time (EXPERIMENTAL)
+    --init                  Add AVA to your project
+    --fail-fast             Stop after first test failure
+    --serial, -s            Run tests serially
+    --tap, -t               Generate TAP output
+    --verbose, -v           Enable verbose output
+    --no-cache              Disable the transpiler cache
+    --no-power-assert       Disable Power Assert
+    --no-color              Disable color output
+    --match, -m             Only run tests with matching title (Can be repeated)
+    --watch, -w             Re-run tests when tests and source files change
+    --timeout, -T           Set global timeout
+    --concurrency, -c       Maximum number of test files running at the same time (EXPERIMENTAL)
+    --update-snapshots, -u  Update snapshots
 
   Examples
     ava
@@ -170,6 +189,21 @@ Directories are recursed, with all `*.js` files being treated as test files. Dir
 
 When using `npm test`, you can pass positional arguments directly `npm test test2.js`, but flags needs to be passed like `npm test -- --verbose`.
 
+
+## Debugging
+
+AVA runs tests in child processes, so to debug tests, you need to do this workaround:
+
+```console
+$ node --inspect node_modules/ava/profile.js some/test/file.js
+```
+
+### Debugger-specific tips
+
+- [Chrome DevTools](docs/recipes/debugging-with-chrome-devtools.md)
+- [WebStorm](docs/recipes/debugging-with-webstorm.md)
+
+
 ## Reporters
 
 ### Mini-reporter
@@ -196,11 +230,15 @@ $ ava --tap | tap-nyan
 
 Please note that the TAP reporter is unavailable when using [watch mode](#watch-it).
 
-### Clean stack traces
+### Magic assert
+
+AVA adds code excerpts and clean diffs for actual and expected values. If values in the assertion are objects or arrays, only a diff is displayed, to remove the noise and focus on the problem. The diff is syntax-highlighted too! If you are comparing strings, both single and multi line, AVA displays a different kind of output, highlighting the added or missing characters.
 
-AVA automatically removes unrelated lines in stack traces, allowing you to find the source of an error much faster.
+![](media/magic-assert-combined.png)
 
-<img src="media/stack-traces.png" width="300">
+### Clean stack traces
+
+AVA automatically removes unrelated lines in stack traces, allowing you to find the source of an error much faster, as seen above.
 
 
 ## Configuration
@@ -225,6 +263,7 @@ All of the CLI options can be configured in the `ava` section of your `package.j
     "concurrency": 5,
     "failFast": true,
     "tap": true,
+    "powerAssert": false,
     "require": [
       "babel-register"
     ],
@@ -235,7 +274,7 @@ All of the CLI options can be configured in the `ava` section of your `package.j
 
 Arguments passed to the CLI will always take precedence over the configuration in `package.json`.
 
-See the [ES2015 support](#es2015-support) section for details on the `babel` option.
+See the [ES2017 support](#es2017-support) section for details on the `babel` option.
 
 ## Documentation
 
@@ -243,15 +282,17 @@ Tests are run concurrently. You can specify synchronous and asynchronous tests.
 
 We *highly* recommend the use of [async functions](#async-function-support). They make asynchronous code concise and readable, and they implicitly return a promise so you don't have to.
 
-If you're unable to use promises or observables, you may enable "callback mode" by defining your test with `test.cb([title], fn)`. Tests declared this way **must** be manually ended with `t.end()`. This mode is mainly intended for testing callback-style APIs.
+If you're unable to use promises or observables, you may enable "callback mode" by defining your test with `test.cb([title], fn)`. Tests declared this way **must** be manually ended with `t.end()`. This mode is mainly intended for testing callback-style APIs. However, we would strongly recommend [promisifying](https://github.com/sindresorhus/pify) callback-style APIs instead of using "callback mode", as this results in more correct and readable tests.
 
 You must define all tests synchronously. They can't be defined inside `setTimeout`, `setImmediate`, etc.
 
-Test files are run from their current directory, so [`process.cwd()`](https://nodejs.org/api/process.html#process_process_cwd) is always the same as [`__dirname`](https://nodejs.org/api/globals.html#globals_dirname). You can just use relative paths instead of doing `path.join(__dirname, 'relative/path')`.
+AVA tries to run test files with their current working directory set to the directory that contains your `package.json` file.
 
 ### Creating tests
 
-To create a test you call the `test` function you imported from AVA. Provide the optional title and implementation function. The function will be called when your test is run. It's passed an [execution object](#t) as its first and only argument. By convention this argument is named `t`.
+To create a test you call the `test` function you imported from AVA. Provide the optional title and implementation function. The function will be called when your test is run. It's passed an [execution object](#t) as its first argument.
+
+**Note:** In order for the [enhanced assertion messages](#enhanced-assertion-messages) to behave correctly, the first argument **must** be named `t`.
 
 ```js
 import test from 'ava';
@@ -317,7 +358,7 @@ test(t => {
 	for (let i = 0; i < 3; i++) {
 		t.true(i < 3);
 	}
-}); // fails, 3 assertions are executed which is too many
+}); // Fails, 3 assertions are executed which is too many
 
 test(t => {
 	t.plan(1);
@@ -325,14 +366,14 @@ test(t => {
 	someAsyncFunction(() => {
 		t.pass();
 	});
-}); // fails, the test ends synchronously before the assertion is executed
+}); // Fails, the test ends synchronously before the assertion is executed
 ```
 
 ### Running tests serially
 
 By default tests are run concurrently, which is awesome. Sometimes though you have to write tests that cannot run concurrently.
 
-In these rare cases you can use the `.serial` modifier. It'll force those tests to run serially *before* the concurrent ones.
+In these rare cases you can use the `.serial` modifier. It will force those tests to run serially *before* the concurrent ones.
 
 ```js
 test.serial(t => {
@@ -386,7 +427,7 @@ Match titles that are *exactly* `foo` (albeit case insensitively):
 $ ava --match='foo'
 ```
 
-Watch titles not containing `foo`:
+Match titles not containing `foo`:
 
 ```console
 $ ava --match='!*foo*'
@@ -421,12 +462,12 @@ test.only('boo will run but not exclusively', t => {
 	t.pass();
 });
 
-// won't run, no title
+// Won't run, no title
 test(function (t) {
 	t.fail();
 });
 
-// won't run, no explicit title
+// Won't run, no explicit title
 test(function foo(t) {
 	t.fail();
 });
@@ -461,7 +502,7 @@ This allows you to merge `.failing` tests before a fix is implemented without br
 ```js
 // See: github.com/user/repo/issues/1234
 test.failing('demonstrate some bug', t => {
-	t.fail(); // test will count as passed
+	t.fail(); // Test will count as passed
 });
 ```
 
@@ -481,35 +522,35 @@ Like `test()` these methods take an optional title and a callback function. The
 
 ```js
 test.before(t => {
-	// this runs before all tests
+	// This runs before all tests
 });
 
 test.before(t => {
-	// this runs after the above, but before tests
+	// This runs after the above, but before tests
 });
 
 test.after('cleanup', t => {
-	// this runs after all tests
+	// This runs after all tests
 });
 
 test.after.always('guaranteed cleanup', t => {
-	// this will always run, regardless of earlier failures
+	// This will always run, regardless of earlier failures
 });
 
 test.beforeEach(t => {
-	// this runs before each test
+	// This runs before each test
 });
 
 test.afterEach(t => {
-	// this runs after each test
+	// This runs after each test
 });
 
 test.afterEach.always(t => {
-	// this runs after each test and other test hooks, even if they failed
+	// This runs after each test and other test hooks, even if they failed
 });
 
 test(t => {
-	// regular test
+	// Regular test
 });
 ```
 
@@ -549,7 +590,7 @@ test(t => {
 });
 ```
 
-By default `t.context` is an object but you can reassign it:
+The context is not shared between tests, allowing you to set up data in a way where it will not risk leaking to other, subsequent tests. By default `t.context` is an object but you can reassign it:
 
 ```js
 test.beforeEach(t => {
@@ -638,21 +679,17 @@ test(t => {
 });
 ```
 
-### ES2015 support
+### ES2017 support
 
-AVA comes with built-in support for ES2015 through [Babel 6](https://babeljs.io). Just write your tests in ES2015. No extra setup needed. You can use any Babel version in your project. We use our own bundled Babel with the [`es2015`](https://babeljs.io/docs/plugins/preset-es2015/) and [`stage-2`](https://babeljs.io/docs/plugins/preset-stage-2/) presets, as well as the [`espower`](https://github.com/power-assert-js/babel-plugin-espower) and [`transform-runtime`](https://babeljs.io/docs/plugins/transform-runtime/) plugins.
+AVA comes with built-in support for ES2017 through [Babel 6](https://babeljs.io). Just write your tests in ES2017. No extra setup needed. You can use any Babel version in your project. We use our own bundled Babel with our [`@ava/stage-4`](https://github.com/avajs/babel-preset-stage-4) and [`stage-2`](https://babeljs.io/docs/plugins/preset-stage-2/) preset, as well as [custom transforms](https://github.com/avajs/babel-preset-transform-test-files) for test and helper files.
 
 The corresponding Babel config for AVA's setup is as follows:
 
 ```json
 {
   "presets": [
-    "es2015",
-    "stage-2"
-  ],
-  "plugins": [
-    "espower",
-    "transform-runtime"
+    "@ava/stage-4",
+    "@ava/transform-test-files"
   ]
 }
 ```
@@ -661,15 +698,15 @@ You can customize how AVA transpiles the test files through the `babel` option i
 
 ```json
 {
-	"ava": {
-		 "babel": {
-			 "presets": [
-					"es2015",
-					"stage-0",
-					"react"
-			 ]
-		 }
-	},
+  "ava": {
+     "babel": {
+       "presets": [
+          "es2015",
+          "stage-0",
+          "react"
+       ]
+     }
+  }
 }
 ```
 
@@ -677,16 +714,16 @@ You can also use the special `"inherit"` keyword. This makes AVA defer to the Ba
 
 ```json
 {
-	"babel": {
-		"presets": [
-			"es2015",
-			"stage-0",
-			"react"
-		]
-	},
-	"ava": {
-		"babel": "inherit"
-	},
+  "babel": {
+    "presets": [
+      "es2015",
+      "stage-0",
+      "react"
+    ]
+  },
+  "ava": {
+    "babel": "inherit"
+  }
 }
 ```
 
@@ -702,9 +739,9 @@ See AVA's [TypeScript recipe](docs/recipes/typescript.md) for a more detailed ex
 
 ### Transpiling imported modules
 
-AVA currently only transpiles the tests you ask it to run. *It will not transpile modules you `import` from outside of the test.* This may be unexpected but there are workarounds.
+AVA currently only transpiles the tests you ask it to run, as well as test helpers (files starting with `_` or in `helpers` directory) inside the test directory. *It will not transpile modules you `import` from outside of the test.* This may be unexpected but there are workarounds.
 
-If you use Babel you can use its [require hook](https://babeljs.io/docs/usage/require/) to transpile imported modules on-the-fly. Run AVA with `--require babel-register` (see [CLI](#cli)) or [configure it in your `package.json`](#configuration).
+If you use Babel you can use its [require hook](https://babeljs.io/docs/usage/require/) to transpile imported modules on-the-fly. To add it, [configure it in your `package.json`](#configuration).
 
 You can also transpile your modules in a separate process and refer to the transpiled files rather than the sources from your tests.
 
@@ -741,7 +778,7 @@ test(async function (t) {
 	t.true(value);
 });
 
-// async arrow function
+// Async arrow function
 test(async t => {
 	const value = await promiseFn();
 	t.true(value);
@@ -759,7 +796,7 @@ test(t => {
 	t.plan(3);
 	return Observable.of(1, 2, 3, 4, 5, 6)
 		.filter(n => {
-			// only even numbers
+			// Only even numbers
 			return n % 2 === 0;
 		})
 		.map(() => t.pass());
@@ -772,7 +809,7 @@ AVA supports using `t.end` as the final callback when using node-style error-fir
 
 ```js
 test.cb(t => {
-	// t.end automatically checks for error as first argument
+	// `t.end` automatically checks for error as first argument
 	fs.readFile('data.txt', t.end);
 });
 ```
@@ -785,7 +822,7 @@ AVA resets a timer after each test, forcing tests to quit if no new test results
 
 You can set timeouts in a human-readable way:
 
-```
+```console
 $ ava --timeout=10s # 10 seconds
 $ ava --timeout=2m # 2 minutes
 $ ava --timeout=100 # 100 milliseconds
@@ -837,7 +874,7 @@ Assertions are mixed into the [execution object](#t) provided to each test imple
 
 ```js
 test(t => {
-	t.truthy('unicorn'); // assertion
+	t.truthy('unicorn'); // Assertion
 });
 ```
 
@@ -877,23 +914,52 @@ Assert that `value` is not equal to `expected`.
 
 ### `.deepEqual(value, expected, [message])`
 
-Assert that `value` is deep equal to `expected`.
+Assert that `value` is deep equal to `expected`. This is based on [Lodash' `isEqual()`](https://lodash.com/docs/4.17.4#isEqual):
+
+> Performs a deep comparison between two values to determine if they are equivalent.
+>
+> *Note*: This method supports comparing arrays, array buffers, booleans, date objects, error objects, maps, numbers, `Object` objects, regexes, sets, strings, symbols, and typed arrays. `Object` objects are compared by their own, not inherited, enumerable properties. Functions and DOM nodes are compared by strict equality, i.e. `===`.
 
 ### `.notDeepEqual(value, expected, [message])`
 
-Assert that `value` is not deep equal to `expected`.
+Assert that `value` is not deep equal to `expected`. The inverse of `.deepEqual()`.
 
 ### `.throws(function|promise, [error, [message]])`
 
 Assert that `function` throws an error, or `promise` rejects with an error.
 
-`error` can be a constructor, regex, error message or validation function.
+`error` can be an error constructor, error message, regex matched against the error message, or validation function.
+
+Returns the error thrown by `function` or a promise for the rejection reason of the specified `promise`.
+
+Example:
+
+```js
+const fn = () => {
+	throw new TypeError('🦄');
+};
+
+test('throws', t => {
+	const error = t.throws(() => {
+		fn();
+	}, TypeError);
+
+	t.is(error.message, '🦄');
+});
+```
+
+```js
+const promise = Promise.reject(new TypeError('🦄'));
 
-Returns the error thrown by `function` or the rejection reason of `promise`.
+test('rejects', async t => {
+	const error = await t.throws(promise);
+	t.is(error.message, '🦄');
+});
+```
 
 ### `.notThrows(function|promise, [message])`
 
-Assert that `function` doesn't throw an `error` or `promise` resolves.
+Assert that `function` does not throw an error or that `promise` does not reject with an error.
 
 ### `.regex(contents, regex, [message])`
 
@@ -907,6 +973,62 @@ Assert that `contents` does not match `regex`.
 
 Assert that `error` is falsy.
 
+### `.snapshot(contents, [message])`
+
+Make a snapshot of the stringified `contents`.
+
+## Snapshot testing
+
+Snapshot testing comes as another kind of assertion and uses [jest-snapshot](https://facebook.github.io/jest/blog/2016/07/27/jest-14.html) under the hood.
+
+When used with React, it looks very similar to Jest:
+
+```js
+// Your component
+const HelloWorld = () => <h1>Hello World...!</h1>;
+
+export default HelloWorld;
+```
+
+```js
+// Your test
+import test from 'ava';
+import render from 'react-test-renderer';
+
+import HelloWorld from '.';
+
+test('HelloWorld component', t => {
+	const tree = render.create(<HelloWorld />).toJSON();
+	t.snapshot(tree);
+});
+```
+
+The first time you run this test, a snapshot file will be created in `__snapshots__` folder looking something like this:
+
+```js
+exports[`HelloWorld component 1`] = `
+<h1>
+	Hello World...!
+</h1>
+`;
+```
+
+These snapshots should be committed together with your code so that everyone on the team shares current state of the app.
+
+Every time you run this test afterwards, it will check if the component render has changed. If it did, it will fail the test.
+
+<img src="media/snapshot-testing.png" width="814">
+
+Then you will have the choice to check your code - and if the change was intentional, you can use the `--update-snapshots` (or `-u`) flag to update the snapshots into their new version.
+
+That might look like this:
+
+```console
+$ ava --update-snapshots
+```
+
+Note that snapshots can be used for much more than just testing components - you can equally well test any other (data) structure that you can stringify.
+
 ### Skipping assertions
 
 Any assertion can be skipped using the `skip` modifier. Skipped assertions are still counted, so there is no need to change your planned assertion count.
@@ -914,7 +1036,7 @@ Any assertion can be skipped using the `skip` modifier. Skipped assertions are s
 ```js
 test(t => {
 	t.plan(2);
-	t.skip.is(foo(), 5); // no need to change your plan count when skipping
+	t.skip.is(foo(), 5); // No need to change your plan count when skipping
 	t.is(1, 1);
 });
 ```
@@ -970,14 +1092,6 @@ Running tests concurrently comes with some challenges, doing file IO is one.
 
 Usually, serial tests create temp directories in the current test directory and clean them up at the end. This won't work when you run tests concurrently as tests will conflict with each other. The correct way to do it is to use a new temp directory for each test. The [`tempfile`](https://github.com/sindresorhus/tempfile) and [`temp-write`](https://github.com/sindresorhus/temp-write) modules can be helpful.
 
-### Debugging
-
-AVA runs tests concurrently by default, which is suboptimal when you need to debug something. Instead, run tests serially with the `--serial` option:
-
-```console
-$ ava --serial
-```
-
 ### Code coverage
 
 You can't use [`istanbul`](https://github.com/gotwarlost/istanbul) for code coverage as AVA [spawns the test files](#process-isolation). You can use [`nyc`](https://github.com/bcoe/nyc) instead, which is basically `istanbul` with support for subprocesses.
@@ -1021,6 +1135,8 @@ It's the [Andromeda galaxy](https://simple.wikipedia.org/wiki/Andromeda_galaxy).
 - [Configuring Babel](docs/recipes/babelrc.md)
 - [Testing React components](docs/recipes/react.md)
 - [JSPM and SystemJS](docs/recipes/jspm-systemjs.md)
+- [Debugging tests with Chrome DevTools](docs/recipes/debugging-with-chrome-devtools.md)
+- [Debugging tests with WebStorm](docs/recipes/debugging-with-webstorm.md)
 
 ## Support
 
@@ -1030,28 +1146,26 @@ It's the [Andromeda galaxy](https://simple.wikipedia.org/wiki/Andromeda_galaxy).
 
 ## Related
 
+- [eslint-plugin-ava](https://github.com/avajs/eslint-plugin-ava) - Lint rules for AVA tests
 - [sublime-ava](https://github.com/avajs/sublime-ava) - Snippets for AVA tests
 - [atom-ava](https://github.com/avajs/atom-ava) - Snippets for AVA tests
 - [vscode-ava](https://github.com/samverschueren/vscode-ava) - Snippets for AVA tests
-- [eslint-plugin-ava](https://github.com/avajs/eslint-plugin-ava) - Lint rules for AVA tests
 - [gulp-ava](https://github.com/avajs/gulp-ava) - Run tests with gulp
 - [grunt-ava](https://github.com/avajs/grunt-ava) - Run tests with grunt
-- [fly-ava](https://github.com/pine/fly-ava) - Run tests with fly
-- [start-ava](https://github.com/start-runner/ava) - Run tests with start
-
-[More...](https://github.com/avajs/awesome-ava#packages)
+- [More…](https://github.com/avajs/awesome-ava#packages)
 
 ## Links
 
 - [Buy AVA stickers](https://www.stickermule.com/user/1070705604/stickers)
 - [Awesome list](https://github.com/avajs/awesome-ava)
-- [JavaScript Air podcast episode](http://jsair.io/ava)
+- [AVA Casts](http://avacasts.com)
+- [More…](https://github.com/avajs/awesome-ava)
 
 ## Team
 
-[![Sindre Sorhus](https://avatars.githubusercontent.com/u/170270?s=130)](http://sindresorhus.com) | [![Vadim Demedes](https://avatars.githubusercontent.com/u/697676?s=130)](https://github.com/vdemedes) | [![James Talmage](https://avatars.githubusercontent.com/u/4082216?s=130)](https://github.com/jamestalmage) | [![Mark Wubben](https://avatars.githubusercontent.com/u/33538?s=130)](https://novemberborn.net) | [![Juan Soto](https://avatars.githubusercontent.com/u/8217766?s=130)](https://juansoto.me)
----|---|---|---|---|---
-[Sindre Sorhus](http://sindresorhus.com) | [Vadim Demedes](https://github.com/vdemedes) | [James Talmage](https://github.com/jamestalmage) | [Mark Wubben](https://novemberborn.net) | [Juan Soto](http://juansoto.me)
+[![Sindre Sorhus](https://avatars.githubusercontent.com/u/170270?s=130)](http://sindresorhus.com) | [![Vadim Demedes](https://avatars.githubusercontent.com/u/697676?s=130)](https://github.com/vadimdemedes) | [![James Talmage](https://avatars.githubusercontent.com/u/4082216?s=130)](https://github.com/jamestalmage) | [![Mark Wubben](https://avatars.githubusercontent.com/u/33538?s=130)](https://novemberborn.net) | [![Juan Soto](https://avatars.githubusercontent.com/u/8217766?s=130)](https://juansoto.me) | [![Jeroen Engels](https://avatars.githubusercontent.com/u/3869412?s=130)](https://github.com/jfmengels)
+---|---|---|---|---|---|---
+[Sindre Sorhus](http://sindresorhus.com) | [Vadim Demedes](https://github.com/vadimdemedes) | [James Talmage](https://github.com/jamestalmage) | [Mark Wubben](https://novemberborn.net) | [Juan Soto](http://juansoto.me) | [Jeroen Engels](https://github.com/jfmengels)
 
 ### Former