summaryrefslogtreecommitdiff
path: root/cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js
diff options
context:
space:
mode:
authorMatt Mastracci <matthew@mastracci.com>2024-02-10 13:22:13 -0700
committerGitHub <noreply@github.com>2024-02-10 20:22:13 +0000
commitf5e46c9bf2f50d66a953fa133161fc829cecff06 (patch)
tree8faf2f5831c1c7b11d842cd9908d141082c869a5 /cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js
parentd2477f780630a812bfd65e3987b70c0d309385bb (diff)
chore: move cli/tests/ -> tests/ (#22369)
This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.
Diffstat (limited to 'cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js')
-rw-r--r--cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js63
1 files changed, 0 insertions, 63 deletions
diff --git a/cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js b/cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js
deleted file mode 100644
index 499f3849f..000000000
--- a/cli/tests/node_compat/test/parallel/test-net-connect-buffer2.js
+++ /dev/null
@@ -1,63 +0,0 @@
-// deno-fmt-ignore-file
-// deno-lint-ignore-file
-
-// Copyright Joyent and Node contributors. All rights reserved. MIT license.
-// Taken from Node 16.13.0
-// This file is automatically generated by "node/_tools/setup.ts". Do not modify this file manually
-
-'use strict';
-const common = require('../common');
-const assert = require('assert');
-const net = require('net');
-
-const tcp = new net.Server(common.mustCall((s) => {
- tcp.close();
-
- let buf = '';
- s.setEncoding('utf8');
- s.on('data', function(d) {
- buf += d;
- });
-
- s.on('end', common.mustCall(function() {
- console.error('SERVER: end', buf);
- assert.strictEqual(buf, "L'État, c'est moi");
- s.end();
- }));
-}));
-
-tcp.listen(0, common.mustCall(function() {
- const socket = new net.Stream({ highWaterMark: 0 });
-
- let connected = false;
- assert.strictEqual(socket.pending, true);
- socket.connect(this.address().port, common.mustCall(() => connected = true));
-
- assert.strictEqual(socket.pending, true);
- assert.strictEqual(socket.connecting, true);
- assert.strictEqual(socket.readyState, 'opening');
-
- // Write a string that contains a multi-byte character sequence to test that
- // `bytesWritten` is incremented with the # of bytes, not # of characters.
- const a = "L'État, c'est ";
- const b = 'moi';
-
- // We're still connecting at this point so the datagram is first pushed onto
- // the connect queue. Make sure that it's not added to `bytesWritten` again
- // when the actual write happens.
- const r = socket.write(a, common.mustCall((er) => {
- console.error('write cb');
- assert.ok(connected);
- assert.strictEqual(socket.bytesWritten, Buffer.from(a + b).length);
- assert.strictEqual(socket.pending, false);
- }));
- socket.on('close', common.mustCall(() => {
- assert.strictEqual(socket.pending, true);
- }));
-
- assert.strictEqual(socket.bytesWritten, Buffer.from(a).length);
- assert.strictEqual(r, false);
- socket.end(b);
-
- assert.strictEqual(socket.readyState, 'opening');
-}));