Comments on: File system mocking for the lazy programmer http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/?&owa_from=feed&owa_sid= Thinking about agile (small 'a') software development, patterns and practices for building Microsoft .NET applications. Wed, 10 Mar 2010 23:02:38 -0800 http://wordpress.org/?v=2.9.2 hourly 1 By: Pages tagged "mocking" http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/comment-page-1/#comment-148 Pages tagged "mocking" Wed, 16 Jan 2008 06:12:53 +0000 http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/#comment-148 [...] = "34d024"; var mooter_wrapper_url=""; var run_method = "onload"; var mooter_target = "0"; Mocking the file system saved by 1 others     Gokuran910000 bookmarked on 01/16/08 | [...]

[...] = “34d024″; var mooter_wrapper_url=”"; var run_method = “onload”; var mooter_target = “0″; Mocking the file system saved by 1 others     Gokuran910000 bookmarked on 01/16/08 | [...]

]]> By: #2782 » Blog Archive » Gotchas: MSTest AppDomain changes in VS 2008 http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/comment-page-1/#comment-144 #2782 » Blog Archive » Gotchas: MSTest AppDomain changes in VS 2008 Sat, 05 Jan 2008 00:17:35 +0000 http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/#comment-144 [...] would have been even simpler to fix and we would have further decoupled our classes. Now that a file system mock is available there’s no reason not to do [...]

[...] would have been even simpler to fix and we would have further decoupled our classes. Now that a file system mock is available there’s no reason not to do [...]

]]> By: Steve Campbell http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/comment-page-1/#comment-132 Steve Campbell Wed, 05 Dec 2007 18:56:34 +0000 http://www.ademiller.com/blogs/tech/2007/12/mocking-the-file-system/#comment-132 I often need to mock out the filesystem, but find it of little use to simply duplicate the filesystem api. Rather, I would treat the filesystem as a service, and make an interface that represented that service. The result is a much higher level interface that allows the code to read much more clearly. (Instead of mocking the filesystem, I mock the service). I often need to mock out the filesystem, but find it of little use to simply duplicate the filesystem api. Rather, I would treat the filesystem as a service, and make an interface that represented that service.

The result is a much higher level interface that allows the code to read much more clearly. (Instead of mocking the filesystem, I mock the service).

]]>