mirror of
https://github.com/nodejs/node.git
synced 2025-05-06 11:29:26 +00:00
52bae222a3
The tap skipping output is so prevalent yet obscure in nature that we ought to move it into it's own function in test/common.js PR-URL: https://github.com/nodejs/node/pull/6697 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
32 lines
1.2 KiB
JavaScript
32 lines
1.2 KiB
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
|
|
if (!common.hasCrypto) {
|
|
common.skip('missing crypto');
|
|
return;
|
|
}
|
|
const crypto = require('crypto');
|
|
const tls = require('tls');
|
|
|
|
process.on('warning', common.mustCall((warning) => {
|
|
assert.strictEqual(warning.name, 'DeprecationWarning');
|
|
assert.notStrictEqual(expected.indexOf(warning.message), -1,
|
|
`unexpected error message: "${warning.message}"`);
|
|
// Remove a warning message after it is seen so that we guarantee that we get
|
|
// each message only once.
|
|
expected.splice(expected.indexOf(warning.message), 1);
|
|
}, 2));
|
|
|
|
var expected = [
|
|
'crypto.Credentials is deprecated. Use tls.SecureContext instead.',
|
|
'crypto.createCredentials is deprecated. Use tls.createSecureContext instead.'
|
|
];
|
|
|
|
// Accessing the deprecated function is enough to trigger the warning event.
|
|
// It does not need to be called. So the assert serves the purpose of both
|
|
// triggering the warning event and confirming that the deprected function is
|
|
// mapped to the correct non-deprecated function.
|
|
assert.strictEqual(crypto.Credentials, tls.SecureContext);
|
|
assert.strictEqual(crypto.createCredentials, tls.createSecureContext);
|