I'm a bit confused how this differs from the existing watch modes that are built into test runners I'm familiar with, such as Jest. Is this something that I'm used to in TypeScript, but which just doesn't exist in most language's ecosystems?
hypertest only runs the tests the were impacted by the changed code. Resulting is blazing fast performance.
I’d say it’s even fast than apples alt+tab animation most of the time.
with all due respect, this is also a solved problem with test watchers. unless you mean this is smart enough to not just run unit tests that are directly related to the file changed, but also understands code changes from the perspective of downstream dependencies?
This is more of a code watcher than a test watcher specifically.
This is not true though. Might depend on the test tooling used, but most of the ones I've used only run changed tests (either directly or through change detection via git, e.g. https://nx.dev/concepts/affected)
How many tests will your system run? That's the important question.
You can’t use it live, And also the analysis granularity is just way too wide compared to this.