While running tests in watch mode, the tests sometimes re-run an indeterminate number of times. Sometimes they don't re-run at all, but sometimes they re-run 3 times or more before settling.
Is there a way, or could we create a way to log which files changed to kick off a re-run?
It seems like this would also require disabling the clearing of the console between re-runs.
This feature would be incredibly useful for hunting down where stray disk-writes are coming from so that they can either be mocked out or ignored with watchPathIgnorePatterns.
While running tests in watch mode, the tests sometimes re-run an indeterminate number of times. Sometimes they don't re-run at all, but sometimes they re-run 3 times or more before settling.
Is there a way, or could we create a way to log which files changed to kick off a re-run?
It seems like this would also require disabling the clearing of the console between re-runs.
This feature would be incredibly useful for hunting down where stray disk-writes are coming from so that they can either be mocked out or ignored with
watchPathIgnorePatterns.