mirror of
https://github.com/nodejs/node.git
synced 2024-11-21 10:59:27 +00:00
caee112e52
There is actually no reason to use `assert.doesNotThrow()` in the tests. If a test throws, just let the error bubble up right away instead of first catching it and then rethrowing it. PR-URL: https://github.com/nodejs/node/pull/18669 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
32 lines
1.1 KiB
JavaScript
32 lines
1.1 KiB
JavaScript
'use strict';
|
||
require('../common');
|
||
|
||
const assert = require('assert');
|
||
const symbol = Symbol('sym');
|
||
|
||
// Verify that getting via a symbol key returns undefined.
|
||
assert.strictEqual(process.env[symbol], undefined);
|
||
|
||
// Verify that assigning via a symbol key throws.
|
||
// The message depends on the JavaScript engine and so will be different between
|
||
// different JavaScript engines. Confirm that the `Error` is a `TypeError` only.
|
||
assert.throws(() => {
|
||
process.env[symbol] = 42;
|
||
}, TypeError);
|
||
|
||
// Verify that assigning a symbol value throws.
|
||
// The message depends on the JavaScript engine and so will be different between
|
||
// different JavaScript engines. Confirm that the `Error` is a `TypeError` only.
|
||
assert.throws(() => {
|
||
process.env.foo = symbol;
|
||
}, TypeError);
|
||
|
||
// Verify that using a symbol with the in operator returns false.
|
||
assert.strictEqual(symbol in process.env, false);
|
||
|
||
// Verify that deleting a symbol key returns true.
|
||
assert.strictEqual(delete process.env[symbol], true);
|
||
|
||
// Checks that well-known symbols like `Symbol.toStringTag` won’t throw.
|
||
Object.prototype.toString.call(process.env);
|