add "test" namespace to node.config.json

[marco-ippolito]

What is the problem this feature will solve?

I was suggested a few times that a test namespace would be beneficial for the test runner.
It could fix issues like #51384

What is the feature you are proposing to solve the problem?

A test namespace with configurations for the test runner, for coverage, filtering etc...
Still need to create a draft of what it could look like

What alternatives have you considered?

none

cc @nodejs/test_runner @cjihrig

[cjihrig]

For additional context:

#51384 is a fairly simple issue to fix from a technical standpoint - allow the test runner to read flags from process.argv instead of only reading from process.execArgv. However, I don't think that should ever be the default behavior because it is inconsistent with how every other Node.js flag is handled. I also don't think it makes sense to add a dedicated CLI flag for that behavior.

If the new config file was capable of setting options that do not correspond to CLI flags, I think this would be a good fit.

[MoLow]

I also wonder if the config file can accept code and not just json values, for example for defining global test hooks, or global state & setup

[marco-ippolito]

I also wonder if the config file can accept code and not just json values, for example for defining global test hooks, or global state & setup

Its a json file so they have to be json properties but you can setup a hook pointing to a file like loaders