/usr/share/doc/ruby-rspec-expectations/features/test_frameworks/minitest.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 50 51 52 | Feature: Minitest integration
rspec-expectations is a stand-alone gem that can be used without the rest of RSpec. If you
like minitest as your test runner, but prefer RSpec's approach to expressing expectations,
you can have both.
To integrate rspec-expectations with minitest, require `rspec/expectations/minitest_integration`.
Scenario: use rspec/expectations with minitest
Given a file named "rspec_expectations_test.rb" with:
"""ruby
require 'minitest/autorun'
require 'rspec/expectations/minitest_integration'
class RSpecExpectationsTest < Minitest::Test
RSpec::Matchers.define :be_an_integer do
match { |actual| Integer === actual }
end
def be_an_int
# This is actually an internal rspec-expectations API, but is used
# here to demonstrate that deprecation warnings from within
# rspec-expectations work correcty without depending on rspec-core
RSpec.deprecate(:be_an_int, :replacement => :be_an_integer)
be_an_integer
end
def test_passing_expectation
expect(1 + 3).to eq 4
end
def test_failing_expectation
expect([1, 2]).to be_empty
end
def test_custom_matcher_with_deprecation_warning
expect(1).to be_an_int
end
def test_using_aggregate_failures
aggregate_failures do
expect(1).to be_even
expect(2).to be_odd
end
end
end
"""
When I run `ruby rspec_expectations_test.rb`
Then the output should contain "4 runs, 5 assertions, 2 failures, 0 errors"
And the output should contain "expected `[1, 2].empty?` to return true, got false"
And the output should contain "be_an_int is deprecated"
And the output should contain "Got 2 failures from failure aggregation block"
|