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
couple of usability quirks I felt when starting with jest.
with mocha, when start tests in --watch mode, all the test run run once and then it waits for further changes to re run. But, with jest, I need to make changes and save for the first run. Since watch is n added functionality to single run, and also we get feedback on current status of codebase before changes, do you think the first behavior is better?
Is it possible to accept update of snapshot in watch mode, without quitting? I like to get feedback on the diff and then just a keypress (say u) to accept the changes. Currently, I have to terminate the watch, update with -u flag, and then start watch mode again.
thanks.
bsr.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Hi,
couple of usability quirks I felt when starting with jest.
--watch
mode, all the test run run once and then it waits for further changes to re run. But, with jest, I need to make changes and save for the first run. Since watch is n added functionality to single run, and also we get feedback on current status of codebase before changes, do you think the first behavior is better?watch
mode, without quitting? I like to get feedback on thediff
and then just a keypress (sayu
) to accept the changes. Currently, I have to terminate the watch, update with-u
flag, and then startwatch
mode again.thanks.
bsr.
The text was updated successfully, but these errors were encountered: