Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: swap assert.strictEqual() parameters #57217

Merged
merged 1 commit into from
Feb 28, 2025

Conversation

lpinca
Copy link
Member

@lpinca lpinca commented Feb 26, 2025

The actual and the expected parameters are respectively the first and the second.

The `actual` and the `expected` parameters are respectively the first
and the second.
@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 Feb 26, 2025
Copy link

codecov bot commented Feb 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.25%. Comparing base (34ded4d) to head (a6deeb5).
Report is 8 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #57217      +/-   ##
==========================================
- Coverage   90.27%   90.25%   -0.02%     
==========================================
  Files         630      630              
  Lines      184634   184634              
  Branches    36128    36120       -8     
==========================================
- Hits       166671   166637      -34     
- Misses      11020    11034      +14     
- Partials     6943     6963      +20     

see 29 files with indirect coverage changes

@aduh95 aduh95 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 Feb 26, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Feb 26, 2025
@nodejs-github-bot
Copy link
Collaborator

@jasnell
Copy link
Member

jasnell commented Feb 26, 2025

I can never remember the order on these. The ship has long sailed off into the distance but I would have much preferred an API like...

assert.value(actual).strictEqual(expected)

Or something similar that makes it a lot clearer... Ah well, good find.

@cjihrig
Copy link
Contributor

cjihrig commented Feb 26, 2025

@jasnell it's never too late for expect() in core (not volunteering).

@nodejs-github-bot
Copy link
Collaborator

@lpinca lpinca added the commit-queue Add this label to land a pull request using GitHub Actions. label Feb 27, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Feb 28, 2025
@nodejs-github-bot nodejs-github-bot merged commit 0d92ce4 into nodejs:main Feb 28, 2025
71 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 0d92ce4

@lpinca lpinca deleted the swap/parameters branch February 28, 2025 10:37
aduh95 pushed a commit that referenced this pull request Mar 9, 2025
The `actual` and the `expected` parameters are respectively the first
and the second.

PR-URL: #57217
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Chemi Atlow <chemi@atlow.co.il>
Reviewed-By: James M Snell <jasnell@gmail.com>
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.

8 participants