fakefs/README.markdown
Chris Wanstrath 1c3a17ccc8 add Home link
2009-10-06 22:00:06 -07:00

103 lines
1.9 KiB
Markdown

FakeFS
======
Mocha is great. But when your library is all about manipulating the
filesystem, you really want to test the behavior and not the implementation.
If you're mocking and stubbing every call to FileUtils or File, you're
tightly coupling your tests with the implementation.
def test_creates_directory
FileUtils.expects(:mkdir).with("directory").once
Library.add "directory"
end
The above test will break if we decide to use `mkdir_p` in our code. Refactoring
code shouldn't necessitate refactoring tests.
With FakeFS:
def test_creates_directory
Library.add "directory"
assert File.directory?("directory")
end
Woot.
Usage
-----
require 'fakefs'
# That's it.
Don't Fake the FS Immediately
-----------------------------
require 'fakefs/safe'
FakeFS.activate!
# your code
FakeFS.deactivate!
# or
FakeFS do
# your code
end
How is this different than MockFS?
----------------------------------
FakeFS provides a test suite and works with symlinks. It's also strictly a
test-time dependency: your actual library does not need to use or know about
FakeFS.
Speed?
------
<http://gist.github.com/156091>
Installation
------------
### [Gemcutter](http://gemcutter.org/)
$ gem install fakefs
### [Rip](http://hellorip.com)
$ rip install git://github.com/defunkt/fakefs.git
Contributors
------------
* Chris Wanstrath
* David Reese
* Jeff Hodges
* Jon Yurek
* Matt Freels
* Myles Eftos
* Pat Nakajima
* Rob Sanheim
* Scott Taylor
* Tymon Tobolski
* msassak
Meta
----
* Code: `git clone git://github.com/defunkt/fakefs.git`
* Home: <http://github.com/defunkt/fakefs>
* Docs: <http://defunkt.github.com/fakefs>
* Bugs: <http://github.com/defunkt/fakefs/issues>
* List: <http://groups.google.com/group/fakefs>
* Test: <http://runcoderun.com/defunkt/fakefs>
* Gems: <http://gemcutter.org/gems/fakefs>
* Boss: Chris Wanstrath :: <http://github.com/defunkt>