Quite common scenario is the tests reading input and/or expected results from files. How can we make sure that changes in those "data files" will trigger re-run of the corresponding tests? Some approaches, with varying degree of success and complexity could be:
- search tests for literals which are filenames
- intercept
open() somehow
- monitor the filesystem during test run