doc: improve the workflow to test release binaries

nodejs · Oct 14, 2022 · 9d715ce · 9d715ce
1 parent 37e5152
commit 9d715ce
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md
@@ -605,10 +605,14 @@ the build before moving forward. Use the following list as a baseline:
 * Run the test suite against the built binaries (optional)
 
 ```console
-./tools/test.py --shell ~/Downloads/node-v18.5.0-linux-x64/bin/node
+ # some tests are relying on the filesystem and the binary name
+ cp ~/Downloads/node-v18.5.0-linux-x64/bin/node ./out/Release/node
+./tools/test.py --shell ./out/Release/node-tmp
 ```
 
-<sup>There may be test issues if the branch used to test does not match the Node.js binary.</sup>
+<sup>There may be test issues if the branch used to test does not match the
+Node.js binary. This usually happen on `test-addon-*` and
+`test-process-config` tests</sup>
 
 ### 11. Tag and sign the release commit