All tests re-run on every change

Environment

1. node -v: 8.11.1

2. npm -v: 5.6.0

3. Operating system: macOS High Sierra

Steps to Reproduce

Save a change to any specific test.

Expected Behavior

Only the changed file’s tests are re-run, leading to quick feedback on test success/failure as a result of the change.

Actual Behavior

All tests in the entire project are re-run, potentially taking a very long time before finding out if the one modified test passes/fails.

This appears to be a regression due to #325 . As one who didn’t have problems with the previous behavior, it would be very nice if this could at least be made an optional setting for those who need it.

[seanpoulter]

The --watch option will use Git or Mercurial to detect the changed files. This is the default mode. Using --watchAll will rerun everything when any file changes. The long game is to:

• add an option in the settings that allows folks who aren’t using Git or Mercurial to use watch mode in some capacity
• detect when jest --watch fails because Git or Mercurial have not been configured and start jest --watch with a notification to the user

I’m unfamiliar with the root cause of #325, but it should be relatively straight forward to investigate.

[seanpoulter]

Also … HUGE thanks for debugging this. 🎉