`node:test` Tests without callback should not be reported as ok

[ClementValot]

Version

26.7.0

Platform

Subsystem

No response

What steps will reproduce the bug?

describe('two todos', () => {
  // TODO
  it('should handle first case', (t) => {
    t.todo();
  });

  // TODO
  it('should handle second case');
});

This would report as

ℹ tests 2
ℹ suites 1
ℹ pass 1
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 1

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

Deterministic

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

A test with no body, thus that doesn't test anything, should not be reported as OK.

It usually indicates a test that's TODO, so the existing feature of reporting todos may be the most relevant option there, and I think (?) it would be non-breaking for existing test suites.

What do you see instead?

TODO/incomplete test reported as pass

Additional information

Hi there 👋

[MoLow]

This does not seem like a bug to me

[ClementValot]

Tbh I did hesitate between bug and feature request.

In the end I trusted my first impression, as someone more experienced with QA and testing than as a developer, the current behavior does not seem suitable.

Impacts include:

• Inflated number of test cases inducing a false sense of security
• Having the "it should do feature A ✅" test marked as pass when it is not testing anything gives at a glance the impression that "feature A" is tested when it is, in fact, not.

To back that up, tests with no callback are marked differently in both mocha and vitest. I'll run a snippet later today to double-check that

[ClementValot]

Confirmed, marked as "pending" in mocha and "todo" in vitest.
No idea about jest.