Commit ad83caf
test: use the correct parameter order on assert.strictEqual()
The parameter order for assert.strictEqual() should be actual, expected
rather than expected, actual which can make test failure messages
confusing. This change reverses the order of the assertion to
match the documented parameter order.
PR-URL: #23520
Reviewed-By: Guy Bedford <guybedford@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>1 parent 100ed74 commit ad83cafCopy full SHA for ad83caf
File tree
Expand file treeCollapse file tree
1 file changed
+3
-3
lines changedOpen diff view settings
Filter options
- test/pummel
Expand file treeCollapse file tree
1 file changed
+3
-3
lines changedOpen diff view settings
Collapse file
test/pummel/test-net-many-clients.js
Copy file name to clipboardExpand all lines: test/pummel/test-net-many-clients.js+3-3Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| ||
70 | 70 | |
71 | 71 | |
72 | 72 | |
73 | | - |
74 | | - |
| 73 | + |
| 74 | + |
75 | 75 | |
76 | 76 | |
77 | 77 | |
| ||
96 | 96 | |
97 | 97 | |
98 | 98 | |
99 | | - |
| 99 | + |
100 | 100 | |
101 | 101 | |
0 commit comments