1+ # This file was generated by the `rspec --init` command. Conventionally, all
2+ # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
3+ # The generated `.rspec` file contains `--require spec_helper` which will cause
4+ # this file to always be loaded, without a need to explicitly require it in any
5+ # files.
6+ #
7+ # Given that it is always loaded, you are encouraged to keep this file as
8+ # light-weight as possible. Requiring heavyweight dependencies from this file
9+ # will add to the boot time of your test suite on EVERY test run, even for an
10+ # individual file that may not need all of that loaded. Instead, consider making
11+ # a separate helper file that requires the additional dependencies and performs
12+ # the additional setup, and require it from the spec files that actually need
13+ # it.
14+ #
15+ # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
16+ RSpec . configure do |config |
17+ # rspec-expectations config goes here. You can use an alternate
18+ # assertion/expectation library such as wrong or the stdlib/minitest
19+ # assertions if you prefer.
20+
21+ config . before ( :context ) { @validate = ENV [ 'TRAVIS_PULL_REQUEST' ] ? '--no-validate' : '--validate' }
22+
23+ config . expect_with :rspec do |expectations |
24+ # This option will default to `true` in RSpec 4. It makes the `description`
25+ # and `failure_message` of custom matchers include text for helper methods
26+ # defined using `chain`, e.g.:
27+ # be_bigger_than(2).and_smaller_than(4).description
28+ # # => "be bigger than 2 and smaller than 4"
29+ # ...rather than:
30+ # # => "be bigger than 2"
31+ expectations . include_chain_clauses_in_custom_matcher_descriptions = true
32+ end
33+
34+ # rspec-mocks config goes here. You can use an alternate test double
35+ # library (such as bogus or mocha) by changing the `mock_with` option here.
36+ config . mock_with :rspec do |mocks |
37+ # Prevents you from mocking or stubbing a method that does not exist on
38+ # a real object. This is generally recommended, and will default to
39+ # `true` in RSpec 4.
40+ mocks . verify_partial_doubles = true
41+ end
42+
43+ # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
44+ # have no way to turn it off -- the option exists only for backwards
45+ # compatibility in RSpec 3). It causes shared context metadata to be
46+ # inherited by the metadata hash of host groups and examples, rather than
47+ # triggering implicit auto-inclusion in groups with matching metadata.
48+ config . shared_context_metadata_behavior = :apply_to_host_groups
49+
50+ # The settings below are suggested to provide a good initial experience
51+ # with RSpec, but feel free to customize to your heart's content.
52+ =begin
53+ # This allows you to limit a spec run to individual examples or groups
54+ # you care about by tagging them with `:focus` metadata. When nothing
55+ # is tagged with `:focus`, all examples get run. RSpec also provides
56+ # aliases for `it`, `describe`, and `context` that include `:focus`
57+ # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
58+ config.filter_run_when_matching :focus
59+ # Allows RSpec to persist some state between runs in order to support
60+ # the `--only-failures` and `--next-failure` CLI options. We recommend
61+ # you configure your source control system to ignore this file.
62+ config.example_status_persistence_file_path = "spec/examples.txt"
63+ # Limits the available syntax to the non-monkey patched syntax that is
64+ # recommended. For more details, see:
65+ # - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
66+ # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
67+ # - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
68+ config.disable_monkey_patching!
69+ # This setting enables warnings. It's recommended, but in some cases may
70+ # be too noisy due to issues in dependencies.
71+ config.warnings = true
72+ # Many RSpec users commonly either run the entire suite or an individual
73+ # file, and it's useful to allow more verbose output when running an
74+ # individual spec file.
75+ if config.files_to_run.one?
76+ # Use the documentation formatter for detailed output,
77+ # unless a formatter has already been configured
78+ # (e.g. via a command-line flag).
79+ config.default_formatter = "doc"
80+ end
81+ # Print the 10 slowest examples and example groups at the
82+ # end of the spec run, to help surface which specs are running
83+ # particularly slow.
84+ config.profile_examples = 10
85+ # Run specs in random order to surface order dependencies. If you find an
86+ # order dependency and want to debug it, you can fix the order by providing
87+ # the seed, which is printed after each run.
88+ # --seed 1234
89+ config.order = :random
90+ # Seed global randomization in this process using the `--seed` CLI option.
91+ # Setting this allows you to use `--seed` to deterministically reproduce
92+ # test failures related to randomization by passing the same `--seed` value
93+ # as the one that triggered the failure.
94+ Kernel.srand config.seed
95+ =end
96+ end
0 commit comments