add --test-timeout flag

[mcollina]

I think adding a --test-timeout 60000 flag is necessary for the test runner to fulfill basic uses cases without requiring a custom runner. It's often the case of having a test that times out, and currently no output is produced in such case.

[koshic]

Agree, it will be very useful for CI (may be with a special exit code).

PS please don't forget to add it to run options

[mcollina]

There is already in run

[shubham9411]

Can I take this one? @mcollina

[mcollina]

Go for it.

[rozzilla]

@mcollina / @shubham9411 do you know if/when this option will be available for Node v.20.x? 😊

[mcollina]

Will be backported in the next few months.

[mcollina]

Actually it will ship today (ideally) #51124

[cjihrig]

I think the implementation of --test-timeout that shipped is not what users would expect. If I were using --test-timeout my expectation (especially based on the documentation) would be for the timeout to be applied to each individual test within a file. What was shipped is a flag that only applies to entire test files.

Consider the following code run with --test-timeout=2000. It correctly times out when used with --test, but passes without --test.

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

test((t, done) => {
  setTimeout(done, 3000);
});