File: to_ary.feature

package info (click to toggle)
ruby-rspec-mocks 2.14.5-1
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 868 kB
  • ctags: 725
  • sloc: ruby: 8,227; makefile: 4
file content (51 lines) | stat: -rw-r--r-- 1,543 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Feature: double handling to_ary

  Ruby implicitly sends `to_ary` to all of the objects in an `Array` when the
  array receives `flatten`:

      [obj].flatten # => obj.to_ary

  If `to_ary` raises a `NoMethodError`, Ruby sees that the object can not be coerced
  into an array and moves on to the next object.

  To support this, an RSpec double will raise a NoMethodError when it receives
  `to_ary` _even if it is set `as_null_object`_, unless `to_ary` is explicitly
  stubbed.

  Scenario: double receiving to_ary
    Given a file named "example.rb" with:
      """ruby
      describe "#to_ary" do
        shared_examples "to_ary" do
          it "can be overridden with a stub" do
            obj.stub(:to_ary) { :non_nil_value }
            obj.to_ary.should be(:non_nil_value)
          end

          it "supports Array#flatten" do
            obj = double('foo')
            [obj].flatten.should eq([obj])
          end
        end

        context "sent to a double as_null_object" do
          let(:obj) { double('obj').as_null_object }
          include_examples "to_ary"

          it "returns nil" do
            expect( obj.to_ary ).to eq nil
          end
        end

        context "sent to a double without as_null_object" do
          let(:obj) { double('obj') }
          include_examples "to_ary"

          it "raises a NoMethodError" do
            expect { obj.to_ary }.to raise_error(NoMethodError)
          end
        end
      end
     """
    When I run `rspec example.rb`
    Then the examples should all pass