You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've set my Jest extension to "jest.runMode": { "type": "on-demand" }, because I've just started using the extension and want it to have a minimal impact on performance. However, I've noticed that, whenever I save a file, it kicks off a test run and comes back with some test failures a few seconds later.
In other words, "on-demand" is doing more what I would have expected "on-save" to do. Am I misunderstanding or misconfiguring something? Or is this a potential bug in the extension?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've set my Jest extension to
"jest.runMode": { "type": "on-demand" }, because I've just started using the extension and want it to have a minimal impact on performance. However, I've noticed that, whenever I save a file, it kicks off a test run and comes back with some test failures a few seconds later.In other words, "on-demand" is doing more what I would have expected "on-save" to do. Am I misunderstanding or misconfiguring something? Or is this a potential bug in the extension?
Beta Was this translation helpful? Give feedback.
All reactions