Contents

Feature: contain_exactly matcher

  The `contain_exactly` matcher provides a way to test arrays against each other
  in a way that disregards differences in the ordering between the actual
  and expected array. For example:

    ```ruby
    expect([1, 2, 3]).to    contain_exactly(2, 3, 1) # pass
    expect([:a, :c, :b]).to contain_exactly(:a, :c ) # fail
    ```

  This matcher is also available as `match_array`, which expects the
  expected array to be given as a single array argument rather than
  as individual splatted elements. The above could also be written as:

    ```ruby
    expect([1, 2, 3]).to    match_array [2, 3, 1] # pass
    expect([:a, :c, :b]).to match_array [:a, :c]  # fail
    ```

  Scenario: array operator matchers
    Given a file named "contain_exactly_matcher_spec.rb" with:
      """ruby
      describe do
        example { expect([1, 2, 3]).to contain_exactly(1, 2, 3) }
        example { expect([1, 2, 3]).to contain_exactly(1, 3, 2) }
        example { expect([1, 2, 3]).to contain_exactly(2, 1, 3) }
        example { expect([1, 2, 3]).to contain_exactly(2, 3, 1) }
        example { expect([1, 2, 3]).to contain_exactly(3, 1, 2) }
        example { expect([1, 2, 3]).to contain_exactly(3, 2, 1) }

        # deliberate failures
        example { expect([1, 2, 3]).to contain_exactly(1, 2, 1) }
      end
      """
     When I run `rspec contain_exactly_matcher_spec.rb`
     Then the output should contain "7 examples, 1 failure"
      And the output should contain:
      """
           Failure/Error: example { expect([1, 2, 3]).to contain_exactly(1, 2, 1) }
             expected collection contained:  [1, 1, 2]
             actual collection contained:    [1, 2, 3]
             the missing elements were:      [1]
             the extra elements were:        [3]
      """

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
rspec-expectations-3.0.0.beta2	features/built_in_matchers/contain_exactly.feature