Ari Perkkiö

Also `--coverage --changed` may run different test files compared to just `--changed`. If there are two test files that cover a single source file, and only one of these test...

Yes, changed (or newly created) files without tests should show up with `0%` coverage. As long as they match the `coverage.include/exclude/all` settings.

> migrate from more old-ish test framework to either Jest or Vitest By the way, Jest also has an option for switching `node:child_process` to `node:worker_threads`. They also link to discussion...

/ecosystem-ci run

Some new errors after rebase 🤔 Oh right, this one is showing up: https://github.com/tinylibs/tinypool/pull/85. Time to update Tinypool to Vitest's repo.

In CI the terminal is not interactive, meaning that terminal cannot be cleared. What is the expected output a dot reporter would produce in this kind of environment? Currently this...

I think we could render the dots of the test final result (green/red) and don't care about test-in-progress states (yellow dots).

Which version of Vitest are you using? Please include it in the System info section. There were some fixes related to this couple of months ago.

I'm unable to reproduce using the repository. In the recording below I let the first 4 tests finish, then click the terminal area and press `p`. Tests are cancelled. https://github.com/vitest-dev/vitest/assets/14806298/ff846277-9543-4b9d-84e7-4844fb9c6ebc...

Pressing the key early enough seems to cause some weird edge case. Tests are not cancelled as early as possible. I'm able to reproduce this now.