When the tests do not produce TAP output, unitest hangs indefinitely on browser tests only.

[lxe]

If the test script doesn't produce TAP output, the --browser tests will hang indefinitely. This does not affect the --node tests.

To demonstrate, create a blank file not-tap-output.js or put some code in it that doesn't produce a tap output:

$ unitest --browser=not-tap-output.js
possibly has some console logs etc....

... hangs

[rtsao]

By default, electron will run indefinitely unless explicitly closed. This is a similar issue to max-mapper/electron-spawn#17

After a quick search I found the following issue (for being able to check if the event loop is empty in electron) but it was marked as wontfix: electron/electron#2358

unitest currently relies on https://github.com/substack/tap-finished to determine when execution has completed.

A default timeout for electron tests could be added, I suppose.

[rtsao]

I think a warning should be logged if no browser test output is found after 5 seconds. This would make it obvious as to why tests would be hanging.