René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Report 0% coverage for untested files in a project (i.e., files matching some glob)","articleBody":"### What is the problem this feature will solve?\n\nRight now, the test runner with `--experimental-code-coverage` doesn't seem to include an entry in the report for files that were not tested at all — i.e., that didn't get loaded during the test execution — even if those files were matched by a `--test-coverage-include` glob.\n\nThis can make the report very misleading, as the reported \"all files\" coverage percentage can easily go up, even when actual coverage has gone down (i.e.,. because a new file was introduced with no tests at all).\n\nI know this has been raised at least [twice](https://github.com/nodejs/help/issues/4487) [before](https://github.com/orgs/nodejs/discussions/4564), but there didn't seem to be any issue for it on the issue tracker, so I wanted to raise it here.\n\n### What is the feature you are proposing to solve the problem?\n\nThere should be some way to have these untested files show up in the report, but report 0% coverage. The effect (although not necessarily the implementation) would be similar to istanbul's [`--all` option](https://github.com/istanbuljs/nyc?tab=readme-ov-file#selecting-files-for-coverage).\n\nI'm not wedded to a particular API, but one reasonable option might be to have a `--test-coverage-include-all` flag that makes sure that any file matched by `--test-coverage-include` shows up in the report.\n\n### What alternatives have you considered?\n\nAs mentioned [here](https://github.com/nodejs/help/issues/4487), it's possible to sort of simulate this effect by passing a glob to `node --test` that covers all the files in the project. However, every file then gets run as a test file, which is a lot of extra overhead, as these files don't actually have any tests.","author":{"url":"https://github.com/ethanresnick","@type":"Person","name":"ethanresnick"},"datePublished":"2025-06-29T18:21:47Z","url":"https://github.com/nodejs/node/issues/58887"}