diff options
author | Matt Mastracci <matthew@mastracci.com> | 2024-02-10 13:22:13 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-02-10 20:22:13 +0000 |
commit | f5e46c9bf2f50d66a953fa133161fc829cecff06 (patch) | |
tree | 8faf2f5831c1c7b11d842cd9908d141082c869a5 /cli/tests/node_compat/test/parallel/test-buffer-bigint64.js | |
parent | d2477f780630a812bfd65e3987b70c0d309385bb (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-buffer-bigint64.js')
-rw-r--r-- | cli/tests/node_compat/test/parallel/test-buffer-bigint64.js | 62 |
1 files changed, 0 insertions, 62 deletions
diff --git a/cli/tests/node_compat/test/parallel/test-buffer-bigint64.js b/cli/tests/node_compat/test/parallel/test-buffer-bigint64.js deleted file mode 100644 index 7aa391f0a..000000000 --- a/cli/tests/node_compat/test/parallel/test-buffer-bigint64.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'; -require('../common'); -const assert = require('assert'); - -const buf = Buffer.allocUnsafe(8); - -['LE', 'BE'].forEach(function(endianness) { - // Should allow simple BigInts to be written and read - let val = 123456789n; - buf[`writeBigInt64${endianness}`](val, 0); - let rtn = buf[`readBigInt64${endianness}`](0); - assert.strictEqual(val, rtn); - - // Should allow INT64_MAX to be written and read - val = 0x7fffffffffffffffn; - buf[`writeBigInt64${endianness}`](val, 0); - rtn = buf[`readBigInt64${endianness}`](0); - assert.strictEqual(val, rtn); - - // Should read and write a negative signed 64-bit integer - val = -123456789n; - buf[`writeBigInt64${endianness}`](val, 0); - assert.strictEqual(val, buf[`readBigInt64${endianness}`](0)); - - // Should read and write an unsigned 64-bit integer - val = 123456789n; - buf[`writeBigUInt64${endianness}`](val, 0); - assert.strictEqual(val, buf[`readBigUInt64${endianness}`](0)); - - // Should throw a RangeError upon INT64_MAX+1 being written - assert.throws(function() { - const val = 0x8000000000000000n; - buf[`writeBigInt64${endianness}`](val, 0); - }, RangeError); - - // Should throw a RangeError upon UINT64_MAX+1 being written - assert.throws(function() { - const val = 0x10000000000000000n; - buf[`writeBigUInt64${endianness}`](val, 0); - }, { - code: 'ERR_OUT_OF_RANGE', - message: 'The value of "value" is out of range. It must be ' + - '>= 0n and < 2n ** 64n. Received 18_446_744_073_709_551_616n' - }); - - // Should throw a TypeError upon invalid input - assert.throws(function() { - buf[`writeBigInt64${endianness}`]('bad', 0); - }, TypeError); - - // Should throw a TypeError upon invalid input - assert.throws(function() { - buf[`writeBigUInt64${endianness}`]('bad', 0); - }, TypeError); -}); |