Title: Setting `"experimental-test-coverage": true` within node.config.json causes multiple reports · Issue #58828 · nodejs/node · GitHub
Open Graph Title: Setting `"experimental-test-coverage": true` within node.config.json causes multiple reports · Issue #58828 · nodejs/node
X Title: Setting `"experimental-test-coverage": true` within node.config.json causes multiple reports · Issue #58828 · nodejs/node
Description: Version 24.3.0 Platform Subsystem No response What steps will reproduce the bug? Create a node.config.json file and include "experimental-test-coverage": true in CLI, run node --experimental-config-file='./node.config.json' --test How of...
Open Graph Description: Version 24.3.0 Platform Subsystem No response What steps will reproduce the bug? Create a node.config.json file and include "experimental-test-coverage": true in CLI, run node --experimental-config...
X Description: Version 24.3.0 Platform Subsystem No response What steps will reproduce the bug? Create a node.config.json file and include "experimental-test-coverage": true in CLI, run node --experimen...
Opengraph URL: https://github.com/nodejs/node/issues/58828
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Setting `\"experimental-test-coverage\": true` within node.config.json causes multiple reports","articleBody":"### Version\n\n24.3.0\n\n### Platform\n\n```text\n\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\n1. Create a node.config.json file and include `\"experimental-test-coverage\": true`\n2. in CLI, run `node --experimental-config-file='./node.config.json' --test`\n\n### How often does it reproduce? Is there a required condition?\n\n100%\n\n### What is the expected behavior? Why is that the expected behavior?\n\nIt behaves like passing the CLI flag `--experimental-test-coverage`.\n\n### What do you see instead?\n\nIt appears the test coverage \"flag\" from the config file is getting passed along to the various sub-processes the test runner spawns, and they are each reporting their own set of tests' coverage. And then at the end, the parent process reports the full coverage.\n\n### Additional information\n\nMerely moving the test coverage flag from config file to cli (leaving other options in the config file) avoids the issue.\n\n\u003cdetails\u003e\n\u003csummary\u003enode.config.test.json\u003c/summary\u003e\n\n```json\n{\n \"$schema\": \"https://nodejs.org/dist/v24.3.0/docs/node-config-schema.json\",\n \"nodeOptions\": {\n \"import\": [\n \"../../test/snapshots.mts\"\n ]\n },\n \"testRunner\": {\n \"experimental-test-coverage\": true,\n \"experimental-test-module-mocks\": true,\n \"test-coverage-exclude\": [\n \"**/test/**\",\n \"**/*.mock.ts\",\n \"**/*.test.ts\"\n ]\n }\n}\n```\n\u003c/details\u003e","author":{"url":"https://github.com/JakobJingleheimer","@type":"Person","name":"JakobJingleheimer"},"datePublished":"2025-06-25T09:13:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/58828/node/issues/58828"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:dbf69f68-dbc3-f99f-f751-3832abd116f5 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D2D4:1CD42A:489AA0B:650055C:6A50D9D2 |
| html-safe-nonce | 7c1eb668315dcc9c5b93bcab48d17a203f038c0d1e8cc0423884e1c51d1daeee |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEMkQ0OjFDRDQyQTo0ODlBQTBCOjY1MDA1NUM6NkE1MEQ5RDIiLCJ2aXNpdG9yX2lkIjoiNjQxMzM4ODMyMzcyNTgyNjUxNSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 7da131e6fea3097b8341e815ab75d25c6b29ce502e575823df3cc59afd149020 |
| hovercard-subject-tag | issue:3174872843 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/58828/issue_layout |
| twitter:image | https://opengraph.githubassets.com/3df9da32b080d1a367a9b016ea468ac24fa3805fe6a3727967e538bcec721c80/nodejs/node/issues/58828 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/3df9da32b080d1a367a9b016ea468ac24fa3805fe6a3727967e538bcec721c80/nodejs/node/issues/58828 |
| og:image:alt | Version 24.3.0 Platform Subsystem No response What steps will reproduce the bug? Create a node.config.json file and include "experimental-test-coverage": true in CLI, run node --experimental-config... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | JakobJingleheimer |
| hostname | github.com |
| expected-hostname | github.com |
| None | 72b13e0e8d0319acdd27a145cfe73f4f06c791713d0ac4690e41fb68ad28cac0 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 73ad5c4eaffed7bb3637024653eabdbca84a855e |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width