the method formerly know as `as_stubbed_constant` was renamed. i updated the readme accordingly.
Update README to replace deprecated methods with their replacement methods
Make the gem's purpose more obvious
Tell me what you do up front. Previously, I had to read through several paragraphs to find out.
Deprecate the old ones, they will be removed in the next major release.
In response to http://stackoverflow.com/questions/15009603/rspec-fire-specs-passing-when-they-shouldnt. We need to load the lib file, and not simply put it on the load path.
Make things work for projects that disable the `should` syntax.
Subclass Module rather than having a giant builder method.
Fix use of const_get/const_defined? to handle undefined consts like Foo::Hash
…oo::Hash. When you name a nested constant that ends in a name that matches a top-level constant (such as "Foo::Hash"), rspec-fire was verifying the presence of a stubbed method on ::Hash if "Foo::Hash" was not defined. 1.9's const_get/const_defined? accepts a flag argument to have it ignore inherited/top-level constants, but 1.8 doesn't accept this argument, so we have to conditionally define methods to handle this properly.
We're only supporting 2.11+ now that it includes constant stubbing support.
Handle strings as well as symbols for method stubs.
Yes, I usually write my method stubs using symbols, but wandered from that path with some simple metaprogramming. RSpec's fine with strings, but rspec-fire wasn't when it came to running my full test suite - it insisted the methods did not exist on the real classes.
Adds MIT License