Skip to content

test_runner: fix coverage function call counts - #67325

Open
Aghayenoor wants to merge 1 commit into
nodejs:mainfrom
Aghayenoor:fix/67319-coverage-function-count
Open

Aghayenoor wants to merge 1 commit into
nodejs:mainfrom
Aghayenoor:fix/67319-coverage-function-count

Conversation

@Aghayenoor

Copy link
Copy Markdown

Use the function range count instead of the maximum block count to keep loop iterations from inflating function call counts.

Add regression coverage for JSON and LCOV reporters with process and none isolation modes.

Fixes: #67319

Use the function range count instead of the maximum block count to keep
loop iterations from inflating function call counts.

Add regression coverage for JSON and LCOV reporters with process and
none isolation modes.

Fixes: nodejs#67319
Assisted-by: GPT-6.1 Sol
Signed-off-by: GreatAg <noorollah.aghayenoor@gmail.com>
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/test_runner

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test_runner Issues and PRs related to the test runner subsystem. labels Nov 7, 2026
@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ci PRs that need a full CI run. test_runner Issues and PRs related to the test runner subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test_runner: coverage reports the largest block count as the function call count (FNDA)

2 participants