In #168 for example the fact that we're only testing FutureFileModule (not files.future) allowed an initialization order bug to slip through. I think that's a somewhat exceptional case, and the lack of coverage is caught by Scoverage, but it would be better not to have to worry about our test code being so abstract that stuff like that can slip through.
In #168 for example the fact that we're only testing
FutureFileModule(notfiles.future) allowed an initialization order bug to slip through. I think that's a somewhat exceptional case, and the lack of coverage is caught by Scoverage, but it would be better not to have to worry about our test code being so abstract that stuff like that can slip through.