CODEWITHSUNDEEP
.netunit-testingtypemock
theDeveloper
theDeveloper

Reputation: 209

Mocking filesystem

If my unit tests rely on the file system and I need to mock this, what is the best way to go about this?

Thanks

Upvotes: 9

Views: 1097

Answers (4)

Eva
Eva

Reputation: 449

Disclaimer I work at Typemock.

I'm glad to say, that our last versions support the following types of System.IO to be mocked:

  • File
  • Directory
  • FileStream

There is a short example:

public void Test()
{
    string path = @"C:\TypemockCan.txt";

    Isolate.WhenCalled(() => File.Exists(null)).WillReturn(true);

    Assert.IsTrue(File.Exists(path));
}

See more examples.

Upvotes: 1

Sam Holder
Sam Holder

Reputation: 32936

This Needed: File system interfaces and implementation in .NET might be useful

Upvotes: 1

Mark Seemann
Mark Seemann

Reputation: 233162

The file system is an excellent example of how TDD can drive you towards a better, more flexible design. Often, when you interact with the file system, you can deal with reading and writing files using Streams or TextWriters instead of actual files.

These are all abstract types and so are easy to mock.

Now you have a more flexible API because it's not tightly coupled to the file system, but still supports file operations.

Upvotes: 9

Anton Gogolev
Anton Gogolev

Reputation: 115779

You basically have two options: eiter abstract all file-system related logic behind a IFileSystemService, or use Stubs from Microsoft, which is

...a lightweight framework for .NET that provides test stubs. For interfaces and non-sealed classes, type-safe wrappers are generated that can be easily customized by attaching delegates.

Upvotes: 3

Related Questions