Sha256: 0e47ac081df4c3f52beb5946903300ac7b7e3a9dd4bad44ccff4a307337c44ec
Contents?: true
Size: 1.38 KB
Versions: 7
Compression:
Stored size: 1.38 KB
Contents
Feature: Null object doubles
[Test doubles](./test-doubles) are strict by default, raising errors when they receive messages that have not
been allowed or expected. You can chain `as_null_object` off of `double` in order to make
the double "loose". For any message that has not explicitly allowed or expected, the double
will return itself. It acts as a block-hole null object, allowing arbitrarily deep method chains.
Scenario: `as_null_object` allows arbitrarily deep message chains and returns itself
Given a file named "as_null_object_spec.rb" with:
"""ruby
RSpec.describe "as_null_object" do
it "returns itself" do
dbl = double("Some Collaborator").as_null_object
expect(dbl.foo.bar.bazz).to be(dbl)
end
end
"""
When I run `rspec as_null_object_spec.rb`
Then the examples should all pass
Scenario: Individual methods can still be allowed or expected
Given a file named "as_null_object_spec.rb" with:
"""ruby
RSpec.describe "as_null_object" do
it "can allow individual methods" do
dbl = double("Some Collaborator", :foo => 3).as_null_object
allow(dbl).to receive(:bar).and_return(4)
expect(dbl.foo).to eq(3)
expect(dbl.bar).to eq(4)
end
end
"""
When I run `rspec as_null_object_spec.rb`
Then the examples should all pass
Version data entries
7 entries across 7 versions & 1 rubygems