TestingHelpers.MockFileSystem level flags to simulate ReadOnly filesystem and Out-Of-Space conditions about system.io.abstractions HOT 4 CLOSED

I think this is beyond the scope of TestingHelpers.MockFileSystem. If you want to test specific interactions in an app, you should use IFileSystem with something like Moq or NSubstitute. MockFileSystem is just a helper for the 99% of cases to save you from having to mock out every last call manually. I'm worried that we're slowly growing the TestHelpers project into an entire in-memory file system.

from system.io.abstractions.

Well, once you had a list of file names and a pointer to their contents, it became an in-memory filesystem. The nice part is that Its a testable file system as well, since in theory, setting up these kinds of scenarios are what make for robust code.

We may have to specifically define what a basic filesystem is, or find a workable definition of it. I would guess that basic filesystem has out-of-space problems, since it has the job of allocating bytes on physical media that has finite space. I dont believe we have to keep track of blocks, but virtual sizes could be summed up and counted against a total size limit.

You could be right though... I believe that to the extent that as long as we dont introduce NTFS semantics into our code, we should be okay. For instance, I dont believe a basic filesystem would have ACLs. And quite possibly, filesystem locking (on the file level) wouldnt exist. Those would technically be mocked, and added to the mockfilesystem itself, since those are semantics associated with a more sophisticated filesystem.

I'm speaking out-of-turn in a sense, because I haven't seen the light on mocking frameworks... most examples I see is making a method in a test that returns exactly what you want, then turn around and test for it...

We should continue discussion.

from system.io.abstractions.

The Helpers are not technically Mocks. They are stubs and should be assumed to behave as such. Be aware that the behavior may not match the behavior expected based on experience with the real implementations. If you need something that is closer in behavior, build it out (and offer up a pull request to contribute back to the library).

Mocking frameworks are great ... :)

from system.io.abstractions.

Going to consider out of scope for now.

from system.io.abstractions.