node/test
Ben Noordhuis 8ec1b0870b crypto: ensure exported webcrypto EC keys use uncompressed point format
The WebCrypto spec apparently mandates that EC keys must be exported in
uncompressed point format. This commit makes it so.

Fixes: https://github.com/nodejs/node/issues/45859
PR-URL: https://github.com/nodejs/node/pull/46021
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
2023-01-01 19:48:51 +01:00
..
abort
addons src: fix creating Isolates from addons 2022-12-23 17:06:05 +00:00
async-hooks
benchmark benchmark: include webstreams benchmark 2022-12-21 16:09:43 +00:00
cctest process,worker: ensure code after exit() effectless 2022-12-25 09:54:12 +00:00
common test: add all WebCryptoAPI globals to WPTRunner's loadLazyGlobals 2022-12-20 13:35:59 +00:00
doctool tools: fix incorrect version history order 2022-12-14 09:38:36 +00:00
embedding
es-module esm: rewrite loader hooks test 2022-12-31 21:23:36 +00:00
fixtures esm: rewrite loader hooks test 2022-12-31 21:23:36 +00:00
fuzzers
internet
js-native-api node-api: generalize finalizer second pass callback 2022-12-20 01:44:42 +08:00
known_issues
message test_runner: add reporters 2022-12-19 17:35:57 +00:00
node-api process,worker: ensure code after exit() effectless 2022-12-25 09:54:12 +00:00
overlapped-checker
parallel crypto: ensure exported webcrypto EC keys use uncompressed point format 2023-01-01 19:48:51 +01:00
pseudo-tty
pummel crypto: use globalThis.crypto over require('crypto').webcrypto 2022-12-16 19:55:42 +00:00
report
sequential bootstrap: make CJS loader snapshotable 2022-12-16 12:44:14 +01:00
testpy
tick-processor
tools
v8-updates
wasi
wpt crypto: ensure exported webcrypto EC keys use uncompressed point format 2023-01-01 19:48:51 +01:00
.eslintrc.yaml crypto: use globalThis.crypto over require('crypto').webcrypto 2022-12-16 19:55:42 +00:00
README.md
root.status

Node.js Core Tests

This directory contains code and data used to test the Node.js implementation.

For a detailed guide on how to write tests in this directory, see the guide on writing tests.

On how to run tests in this directory, see the contributing guide.

For the tests to run on Windows, be sure to clone Node.js source code with the autocrlf git config flag set to true.

Test Directories

Directory Runs on CI Purpose
abort Yes Tests that use --abort-on-uncaught-exception and other situations where we want to test something but avoid generating a core file.
addons Yes Tests for addon functionality along with some tests that require an addon.
async-hooks Yes Tests for async_hooks functionality.
benchmark Yes Test minimal functionality of benchmarks.
cctest Yes C++ tests that are run as part of the build process.
code-cache No Tests for a Node.js binary compiled with V8 code cache.
common Common modules shared among many tests. Documentation
doctool Yes Tests for the documentation generator.
es-module Yes Test ESM module loading.
fixtures Test fixtures used in various tests throughout the test suite.
internet No Tests that make real outbound network connections. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections.
js-native-api Yes Tests for Node.js-agnostic Node-API functionality.
known_issues Yes Tests reproducing known issues within the system. All tests inside of this directory are expected to fail. If a test doesn't fail on certain platforms, those should be skipped via known_issues.status.
message Yes Tests for messages that are output for various conditions (console.log, error messages etc.)
node-api Yes Tests for Node.js-specific Node-API functionality.
parallel Yes Various tests that are able to be run in parallel.
pseudo-tty Yes Tests that require stdin/stdout/stderr to be a TTY.
pummel No Various tests for various modules / system functionality operating under load.
sequential Yes Various tests that must not run in parallel.
testpy Test configuration utility used by various test suites.
tick-processor No Tests for the V8 tick processor integration. The tests are for the logic in lib/internal/v8_prof_processor.js and lib/internal/v8_prof_polyfill.js. The tests confirm that the profile processor packages the correct set of scripts from V8 and introduces the correct platform specific logic.
v8-updates No Tests for V8 performance integration.