[Enter] key in watch mode has unexpected behavior

[nathanmmiller]

In both jest and vitest, when running watch mode, you can specify a filter to run on via 'p' or 't'. For example, you may have run watch mode on all tests but decide you want only to rerun foo.test.js for a while, so you'd type 'p' and then type 'foo' and [enter] and go from there. On every subsequent rerun, it should run only foo.test.js until you leave that filter.

In jest, this works as expected - a rerun caused by HMR or by the [enter] key will run only foo.test.js.
In vitest, this only half works as expected - a rerun caused by HMR will run only foo.test.js. However, a rerun caused by the [enter] key will rerun all tests. Oddly, this does not clear the filter. Once all tests are done, HMR will again rerun only foo.test.js.

I believe this is a bug - I believe that [enter] in a watch mode terminal should respect any current filters.

[sheremet-va]

enter reruns all tests in Vitest (note "return"):

[nathanmmiller]

Ah ok so this is not a bug then. I should just use 'r' instead of 'enter'. Will close the discussion.