Commit feec26d
test: use mustSucceed in test-fs-read
This commit refactors the callback in test/parallel/test-fs-read.js
to use common.mustSucceed() instead of common.mustCall().
common.mustSucceed() is the preferred helper for standard error-first
callbacks that are expected to succeed, as it provides an explicit
check that the `err` argument is null. This improves the clarity
and robustness of the test.
PR-URL: #59204
Reviewed-By: Zeyu "Alex" Yang <himself65@outlook.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent b30a211 commit feec26d
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -8,7 +8,7 @@ const fd = fs.openSync(filepath, 'r'); | |||
| 8 | 8 | const bufferAsync = Buffer.alloc(0); | |
| 9 | 9 | const bufferSync = Buffer.alloc(0); | |
| 10 | 10 | ||
| 11 | - fs.read(fd, bufferAsync, 0, 0, 0, common.mustCall((err, bytesRead) => { | ||
| 11 | + fs.read(fd, bufferAsync, 0, 0, 0, common.mustSucceed((bytesRead) => { | ||
| 12 | 12 | assert.strictEqual(bytesRead, 0); | |
| 13 | 13 | assert.deepStrictEqual(bufferAsync, Buffer.alloc(0)); | |
| 14 | 14 | })); | |
0 commit comments