test runner (--test, node:test) subtest test context lack `.skip`, `.only` and `.todo` functions

[soanvig]

Version

20.7.0

Platform

Linux void-desktop 6.5.9_1 #1 SMP PREEMPT_DYNAMIC Thu Oct 26 12:11:50 UTC 2023 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

const test = require('node:test');

test('Parent', t => {
	t.test.only('Child only', () => {});
	t.test.skip('Child skip', () => {});
	t.test.todo('Child todo', () => {});
});

Run with node --test <file> (same result without the --test flag)

How often does it reproduce? Is there a required condition?

Consistently

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

All functions work as described here: https://nodejs.org/docs/latest-v20.x/api/test.html#subtests

This method behaves identically to the top level test() function. The following example demonstrates the creation of a top level test with two subtests.

What do you see instead?

TypeError [Error]: t.test.todo is not a function

TypeError [Error]: t.test.skip is not a function

TypeError [Error]: t.test.only is not a function

Additional information

These functions work for top-level test, they don't work for nested tests.
Maybe it doesn't make sense to expose those functions for subtests (use just describe - maybe it's enough), but in that case the documentation is misleading

[rluvaton]

@marco-ippolito I think it should be a bug, no?

Creating a fix now

[marco-ippolito]

@marco-ippolito I think it should be a bug, no?

Creating a fix now

I don't think it's a bug, I think these function are not implemented in non-root tests
cc @nodejs/test_runner

[rluvaton]

I think it is a bug as the docs specifically state that it should work:

This method behaves identically to the top level test()