From ad5cdd5c7484909cf6a24ba891898870f2503753 Mon Sep 17 00:00:00 2001 From: Gilad Hoshmand Date: Tue, 20 May 2025 13:55:54 +0300 Subject: [PATCH] Update collecting-code-coverage.md Signed-off-by: Gilad Hoshmand --- .../site/pages/en/learn/test-runner/collecting-code-coverage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/learn/test-runner/collecting-code-coverage.md b/apps/site/pages/en/learn/test-runner/collecting-code-coverage.md index 03d5e99c9afcf..91361d666e2c8 100644 --- a/apps/site/pages/en/learn/test-runner/collecting-code-coverage.md +++ b/apps/site/pages/en/learn/test-runner/collecting-code-coverage.md @@ -6,7 +6,7 @@ authors: avivkeller # Collecting code coverage in Node.js -Node.js provides built-in support for code coverage through its test runner, which can be enabled using the [`--experimental-code-coverage`](https://nodejs.org/api/cli.html#--experimental-test-coverage) flag. +Node.js provides built-in support for code coverage through its test runner, which can be enabled using the [`--experimental-test-coverage`](https://nodejs.org/api/cli.html#--experimental-test-coverage) flag. If using the `run()` API, the `coverage` option must be set to `true`. For more information on the `run()` API, see [the `node:test` documentation](https://nodejs.org/docs/latest/api/test.html#runoptions).