Jimfs support for JUnit 5 `TempDirFactory` about jimfs HOT 4 OPEN

Sorry. I'm not sure if I understand what I mean, either :) My thinking was roughly that there might be a way to write a single annotation that could tell JUnit to use an arbitrary given FileSystem implementation, perhaps one pulled from a field in the test class. But this all needs more thought. If we do start adopting JUnit 5 at some point, we may take a look.

from jimfs.

Interesting, thanks. Cool that jimfs makes the JUnit docs!

We're not JUnit 5 users (yet? unclear :)), so it probably won't be a priority, but that's not to rule it out entirely. (If nothing else, it makes it harder for us to judge design questions like "Should it be able to use a FileSystem from the test?" and "If so, might it be even better as a filesystem-agnostic utility than as one specific to jimfs?") We can see what demand arises, and then... who knows? :)

from jimfs.

We're not JUnit 5 users (yet? unclear :)), so it probably won't be a priority, but that's not to rule it out entirely.

I see, at least you're now aware of it 🙂

it makes it harder for us to judge design questions like "Should it be able to use a FileSystem from the test?" and "If so, might it be even better as a filesystem-agnostic utility than as one specific to jimfs?"

Not sure I fully understood what you mean. I personally consider relying on an in-memory file system in tests a common use case and that was one of my motivations for the changes I proposed to the JUnit 5 team.

Just to point to a real-life example of a TempDirFactory usage, your "competitor" memoryfilesystem offers now a JUnit 5 specific module: https://github.com/marschall/memoryfilesystem-junit-provider

from jimfs.