From f5e46c9bf2f50d66a953fa133161fc829cecff06 Mon Sep 17 00:00:00 2001
From: Matt Mastracci <matthew@mastracci.com>
Date: Sat, 10 Feb 2024 13:22:13 -0700
Subject: 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.
---
 .../test/parallel/test-child-process-spawn-args.js | 62 ----------------------
 1 file changed, 62 deletions(-)
 delete mode 100644 cli/tests/node_compat/test/parallel/test-child-process-spawn-args.js

(limited to 'cli/tests/node_compat/test/parallel/test-child-process-spawn-args.js')

diff --git a/cli/tests/node_compat/test/parallel/test-child-process-spawn-args.js b/cli/tests/node_compat/test/parallel/test-child-process-spawn-args.js
deleted file mode 100644
index e2597c921..000000000
--- a/cli/tests/node_compat/test/parallel/test-child-process-spawn-args.js
+++ /dev/null
@@ -1,62 +0,0 @@
-// deno-fmt-ignore-file
-// deno-lint-ignore-file
-
-// Copyright Joyent and Node contributors. All rights reserved. MIT license.
-// Taken from Node 18.12.1
-// This file is automatically generated by `tools/node_compat/setup.ts`. Do not modify this file manually.
-
-'use strict';
-
-// This test confirms that `undefined`, `null`, and `[]`
-// can be used as a placeholder for the second argument (`args`) of `spawn()`.
-// Previously, there was a bug where using `undefined` for the second argument
-// caused the third argument (`options`) to be ignored.
-// See https://github.com/nodejs/node/issues/24912.
-
-const common = require('../common');
-const tmpdir = require('../common/tmpdir');
-
-const assert = require('assert');
-const { spawn } = require('child_process');
-
-tmpdir.refresh();
-
-const command = common.isWindows ? 'cd' : 'pwd';
-const options = { cwd: tmpdir.path };
-
-if (common.isWindows) {
-  // This test is not the case for Windows based systems
-  // unless the `shell` options equals to `true`
-
-  options.shell = true;
-}
-
-const testCases = [
-  undefined,
-  null,
-  [],
-];
-
-const expectedResult = tmpdir.path.trim().toLowerCase();
-
-(async () => {
-  const results = await Promise.all(
-    testCases.map((testCase) => {
-      return new Promise((resolve) => {
-        const subprocess = spawn(command, testCase, options);
-
-        let accumulatedData = Buffer.alloc(0);
-
-        subprocess.stdout.on('data', common.mustCall((data) => {
-          accumulatedData = Buffer.concat([accumulatedData, data]);
-        }));
-
-        subprocess.stdout.on('end', () => {
-          resolve(accumulatedData.toString().trim().toLowerCase());
-        });
-      });
-    })
-  );
-
-  assert.deepStrictEqual([...new Set(results)], [expectedResult]);
-})().then(common.mustCall());
-- 
cgit v1.2.3