Groups the methods for interception together this is a mix-in for the created isolations for classes
Verifies whether the specified method has been called You can specify constraints in the block
The most complex configuration you can make currently is one that is constrained by arguments. This is most likely to be extended in the future to allow for more complex verifications.
Example:
an_isolation.did_receive?(:a_method) do |method_call| method_call.with(3, "a") end.should.be.successful
is equivalent to:
an_isolation.did_receive?(:a_method).with(3, "a").should.be.successful
You will probably be using this method only when you’re interested in whether a method has been called during the course of the test you’re running.
# File lib/caricature/isolator.rb, line 69 def did_receive?(method_name, &block) isolation_context.verify method_name end
the context of this isolation instance. this context takes care of responding to method calls etc.
# File lib/caricature/isolator.rb, line 28 def isolation_context self.class.isolation_context end
Replaces the call to the proxy with the one you create with this method. You can specify more specific criteria in the block to configure the expectation.
Example:
an_isolation.when_receiving(:a_method) do |method_call| method_call.with(3, "a").return(5) end
is equivalent to:
an_isolation.when_receiving(:a_method).with(3, "a").return(5)
You will most likely use this method when you want your stubs to return something else than nil when they get called during the run of the test they are defined in.
# File lib/caricature/isolator.rb, line 47 def when_receiving(method_name, &block) isolation_context.create_override method_name, &block end
Disabled; run with --debug to generate this.
Generated with the Darkfish Rdoc Generator 1.1.6.