| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
|
//cc @nodejs/test_runner |
Sorry, something went wrong.
There was a problem hiding this comment.
How does --test affect --require, or loaders? What happens to the REPL with node --test and no other arguments?
If NODE_OPTIONS='--test' is set, and the user doesn't control how node is invoked (via a shebang, for example), does this mean the user can never "undo" test mode?
This really feels to me like it should be an entirely distinct binary, rather than just a "mode" of the main node binary.
Sorry, something went wrong.
As this PR currently is --test hasn't been added to the allow list for NODE_OPTIONS so setting it there would throw an error. |
Sorry, something went wrong.
|
@richardlau thanks, if that's explicitly going to never be allowed there then that does mitigate that one concern, but all the others remain. |
Sorry, something went wrong.
node --test doesn't launch the REPL. I haven't tried a loader, but --require seems to work fine.
--test in NODE_OPTIONS explicitly errors out. |
Sorry, something went wrong.
There was a problem hiding this comment.
Just a question: why is this? I can definitely see wanting to run the inspector for debugging while running tests.
Sorry, something went wrong.
There was a problem hiding this comment.
A couple reasons:
Sorry, something went wrong.
There was a problem hiding this comment.
Can we use chrome's debugger blackboxing stuff to "hide" the test runner code when inspecting?
Sorry, something went wrong.
There was a problem hiding this comment.
Possibly - I'm not sure though.
Sorry, something went wrong.
This commit introduces an initial version of a CLI-based test runner. PR-URL: nodejs#42658 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
This commit introduces an initial version of a CLI-based test runner. PR-URL: #42658 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Notable changes: doc: * add @kuriyosh to collaborators (Yoshiki Kurihara) #42824 lib,src: * (SEMVER-MINOR) implement WebAssembly Web API (Tobias Nießen) #42701 test_runner: * (SEMVER-MINOR) add initial CLI runner (Colin Ihrig) #42658 worker: * (SEMVER-MINOR) add hasRef() to MessagePort (Darshan Sen) #42849 PR-URL: #42943
Notable changes: doc: * add @kuriyosh to collaborators (Yoshiki Kurihara) #42824 lib,src: * (SEMVER-MINOR) implement WebAssembly Web API (Tobias Nießen) #42701 test_runner: * (SEMVER-MINOR) add initial CLI runner (Colin Ihrig) #42658 worker: * (SEMVER-MINOR) add hasRef() to MessagePort (Darshan Sen) #42849 PR-URL: #42943
|
Who will extend the @types/node package with a new node:test module? |
Sorry, something went wrong.
As always, the maintainers of https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node. |
Sorry, something went wrong.
This commit introduces an initial version of a CLI-based test runner. PR-URL: nodejs#42658 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
This commit introduces an initial version of a CLI-based test runner. PR-URL: nodejs/node#42658 Backport-PR-URL: nodejs/node#43904 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
| Back | FazBrowse Home | New Git URL |
This commit introduces an initial version of a CLI-based test runner.