Skip to content

Conversation

@Renegade334
Copy link
Member

The new --eval tests for util.parseArgs() are genuine usage tests that spawn a node instance with command-line args, whereas the existing test for "command-line parsing" just overwrites process.argv. Mocking this property is fine for the input parsing tests, but the command-line behaviour should also be genuinely tested here.

Refs: #60814

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels Dec 16, 2025
@codecov
Copy link

codecov bot commented Dec 16, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.51%. Comparing base (4f24aff) to head (c5b8174).
⚠️ Report is 73 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #61089      +/-   ##
==========================================
- Coverage   88.53%   88.51%   -0.02%     
==========================================
  Files         703      703              
  Lines      208546   208546              
  Branches    40217    40224       +7     
==========================================
- Hits       184634   184594      -40     
- Misses      15926    15962      +36     
- Partials     7986     7990       +4     

see 47 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@avivkeller avivkeller added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Dec 28, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Dec 28, 2025
@nodejs-github-bot
Copy link
Collaborator

@@ -1,4 +1,5 @@
import { spawnPromisified } from '../common/index.mjs';
import { path } from '../common/fixtures.mjs';
Copy link
Contributor

@aduh95 aduh95 Dec 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: path is usually referring to node:path, it's confusing to have it refer to a function

Suggested change
import { path } from '../common/fixtures.mjs';
import * as fixtures from '../common/fixtures.mjs';

EDIT: I guess it should be a follow up along with a lint rule

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both patterns are in common use at the moment, I don't mind changing but it will need following up in either case.

@nodejs-github-bot
Copy link
Collaborator

@aduh95 aduh95 added the commit-queue Add this label to land a pull request using GitHub Actions. label Dec 30, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Dec 30, 2025
@nodejs-github-bot nodejs-github-bot merged commit 7b7f693 into nodejs:main Dec 30, 2025
79 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 7b7f693

@Renegade334 Renegade334 deleted the test-parseargs-exec branch December 30, 2025 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. needs-ci PRs that need a full CI run. test Issues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants