test_runner: todo/skip/expectFailure are truthy per docs, but implementation is otherwise

Version

v25.6.1

Subsystem

node:test

What steps will reproduce the bug?

Add the todo, skip or testFailure option to a test, setting it to an empty string. The result will be the same as if you set it to true or a non-empty string.

What is the expected behavior? Why is that the expected behavior?

Unsure whether the bug is in the code or in the API docs.

The code clearly does not treat these options as truthy:
https://github.com/nodejs/node/blob/2de34822cc9a19621a663e3f22b00b9a01697635/lib/internal/test_runner/test.js#L639-L641

But the docs specifically state they should be:

https://github.com/nodejs/node/blob/2de34822cc9a19621a663e3f22b00b9a01697635/doc/api/test.md?plain=1#L1691-L1696

Additional information

Previous discussions:

• Three years ago: https://github.com/nodejs/node/pull/47537#pullrequestreview-1383887199 @ljharb
• More recently as part of expectFailure development: https://github.com/nodejs/test-runner/pull/10#discussion_r2739831598 @JakobJingleheimer

Inizia da lib/internal/test_runner/test.js intorno alle righe 639-641 e dalle descrizioni delle opzioni in doc/api/test.md intorno alle righe 1691-1696. Esamina le discussioni collegate per determinare se le stringhe vuote debbano essere considerate abilitate o se la documentazione sia errata. Il lavoro è completato quando la documentazione e l'implementazione concordano e sono presenti test per i valori vuoti, true e non vuoti.