Testing real behavior of node by running sample http server application. #159
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
irbull
force-pushed
the
master
branch
3 times, most recently
from
cd57118 to
4b8e529
Compare
RamsesAupart
approved these changes
Aug 15, 2025
RamsesAupart
approved these changes
Aug 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The existing
NodeJSTestis a bit trivial, testing just export and access to global object. Here is a test that is more node.js-like.The test executes sample node.js hello world application - e.g. an HTTP server. Then it connects to it and verifies it really runs properly. The test is started on a free port to avoid conflicts with any local configuration.