Best practices for file system dependencies in unit/integration tests

Question

I just started writing tests for a lot of code. There\'s a bunch of classes with dependencies to the file system, that is they read CSV files, read/write configuration files

Answer 1

Give the test files, both in and out, names that are structurally similar to the unit test name.

In JUnit, for instance, I'd use:

File reportFile = new File("tests/output/" + getClass().getSimpleName() + "/" + getName() + ".report.html");