From 15110bfc664250f1e3308b903ea373f59dfcd32d Mon Sep 17 00:00:00 2001 From: Avinash Kumar Date: Tue, 5 Dec 2023 00:07:17 +0530 Subject: [PATCH] Update 03-assertions.md Adding text in assertion planning in order to inform about ava assertion not stopping even when they fail linked to issue (document that ava assertions don't throw #2624) --- docs/03-assertions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-assertions.md b/docs/03-assertions.md index 1613658ec..c4408a511 100644 --- a/docs/03-assertions.md +++ b/docs/03-assertions.md @@ -35,7 +35,7 @@ Assertion plans ensure tests only pass when a specific number of assertions have If you do not specify an assertion plan, your test will still fail if no assertions are executed. Set the `failWithoutAssertions` option to `false` in AVA's [`package.json` configuration](./06-configuration.md) to disable this behavior. -Note that, unlike [`tap`](https://www.npmjs.com/package/tap) and [`tape`](https://www.npmjs.com/package/tape), AVA does *not* automatically end a test when the planned assertion count is reached. +Note that, unlike [`tap`](https://www.npmjs.com/package/tap) and [`tape`](https://www.npmjs.com/package/tape), AVA does *not* automatically end a test when the planned assertion count is reached. Note that ava assertions *don't* stop the test when they fail for better analysis of your code These examples will result in a passed test: