doc: update todo test behaviour

[pulkit-30]

ref: #49013 (comment)

[nodejs-github-bot]

Review requested:

• @nodejs/test_runner

[aduh95]

I think the idea is to still get the test result, otherwise there are no distinction between skip and todo and we might as keep only one 🤔

[marco-ippolito]

Todo test should fail but not exit with code 1, not affecting the result. Making it a noop makes it just an alias of skip.
I think there is a bug that makes todo test exit

[pulkit-30]

I think the idea is to still get the test result, otherwise there are no distinction between skip and todo and we might as keep only one 🤔

I think running a todo test doesn't make any sense as it will fails coz it's not fully implemented or maybe planned to write it later on.

One thing that we can do to make a distinction between skip and todo as to restrict user to not pass test fn when test is marked as todo (similar to jest-todo).

[pulkit-30]

Todo test should fail but not exit with code 1, not affecting the result.

+1

[pulkit-30]

Todo test should fail but not exit with code 1, not affecting the result. Making it a noop makes it just an alias of skip. I think there is a bug that makes todo test exit

I found that todo test runs and does not terminate execution of the test function. also if it fails it doesnot mark exitCode as 1.
I have documented this behavior coz i didn't find anything about this.

[marco-ippolito]

I'm not sure the wording is right.
AFAIK the failure of a test does not terminate the execution it makes exit code 1.
Saying that todo does not terminate it imples that failure do which I dont think is correct

[jasnell]

Suggested change

	**Note:** Running a `todo` test does not terminate the execution of the test
	Running a `todo` test does not terminate the execution of the test

[MoLow]

Should this be superseded by #52204?

[cjihrig]

Closing per the previous comment.