Sadly Continuous Testing still not fast in @JetBrainsRider 2019.1 EAP 1 @NCrunch 3.24 needs 3 Seconds (after typing) to display result of a simple test, Rider needs 8 Seconds (after Save) to display the result. .NET Core 2.2, tests running on local machine. @matkoch87
The way the IDE integration is built often depends a lot of the test runner. With Jest, we are lucky to have very nice APIs. But there's definitely always a room for improvement.
-
-
Yes, but other tools in the .net world are a lot faster than Rider. So I tell them and hope for improvement
-
Then I don't think that
@jetbrains likes to be at the third position ;) - 3 more replies
New conversation -
-
-
I've run the Jest test with --watch-all, then Jest Console is interactive and it is possible to change what is running (all, only change etc.) it is not possible to give keyboard input within WebStorm from the runner.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.