Disable jest watch mode when --coverage flag is present [#1207] #1229
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the enhancement described in #1207.
I just added this condition to the addition of the '--watch' flag in the test script. I tested this on my computer and it seems to do the trick, i'm guessing the rest is handled by Jest (make all the tests run when not in watch mode, versus only run tests modified since last commit when watch mode is active).
If there's something I forgot, please let me know.
Also I ran the tasks/e2e.sh script, and it hangs on line 181
npm run test -- --watch=no
because it does, in fact, run in watch mode. You have to press 'q' for the script to continue. Is this normal or a regression I introduced ? This seems to be true even on master...Finally, is there something to add to test the new behavior?