/usr/share/doc/ruby-rspec-expectations/features/built_in_matchers/match.feature is in ruby-rspec-expectations 3.4.0c3e0m1s1-1ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 | Feature: `match` matcher
The `match` matcher calls `#match` on the object, passing if `#match` returns a truthy (not
`false` or `nil`) value. `Regexp` and `String` both provide a `#match` method.
```ruby
expect("a string").to match(/str/) # passes
expect("a string").to match(/foo/) # fails
expect(/foo/).to match("food") # passes
expect(/foo/).to match("drinks") # fails
```
You can also use this matcher to match nested data structures when composing matchers.
Scenario: string usage
Given a file named "string_match_spec.rb" with:
"""ruby
RSpec.describe "a string" do
it { is_expected.to match(/str/) }
it { is_expected.not_to match(/foo/) }
# deliberate failures
it { is_expected.not_to match(/str/) }
it { is_expected.to match(/foo/) }
end
"""
When I run `rspec string_match_spec.rb`
Then the output should contain all of these:
| 4 examples, 2 failures |
| expected "a string" not to match /str/ |
| expected "a string" to match /foo/ |
Scenario: regular expression usage
Given a file named "regexp_match_spec.rb" with:
"""ruby
RSpec.describe /foo/ do
it { is_expected.to match("food") }
it { is_expected.not_to match("drinks") }
# deliberate failures
it { is_expected.not_to match("food") }
it { is_expected.to match("drinks") }
end
"""
When I run `rspec regexp_match_spec.rb`
Then the output should contain all of these:
| 4 examples, 2 failures |
| expected /foo/ not to match "food" |
| expected /foo/ to match "drinks" |
|