test: formalize exposure of internal bindings
moves exposed internalBinding
s to a single location with short
guidelines on how to expose them and a warning for users should they
come across it.
i would also like to take this opportunity to discuss if these tests are needed. traditionally it seems we rely on internals working by ensuring the behavior of the publicly facing apis that depend on them, but after there was a bug with module_wrap i was encouraged to create a test for it.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
tests and/or benchmarks are included -
commit message follows commit guidelines