1require "codeclimate-test-reporter"
 2CodeClimate::TestReporter.start
 3# This file was generated by the `rails generate rspec:install` command. Conventionally, all
 4# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
 5# The generated `.rspec` file contains `--require spec_helper` which will cause this
 6# file to always be loaded, without a need to explicitly require it in any files.
 7#
 8# Given that it is always loaded, you are encouraged to keep this file as
 9# light-weight as possible. Requiring heavyweight dependencies from this file
10# will add to the boot time of your test suite on EVERY test run, even for an
11# individual file that may not need all of that loaded. Instead, consider making
12# a separate helper file that requires the additional dependencies and performs
13# the additional setup, and require it from the spec files that actually need it.
14#
15# The `.rspec` file also contains a few flags that are not defaults but that
16# users commonly want.
17#
18# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
19RSpec.configure do |config|
20  # rspec-expectations config goes here. You can use an alternate
21  # assertion/expectation library such as wrong or the stdlib/minitest
22  # assertions if you prefer.
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# The settings below are suggested to provide a good initial experience
44# with RSpec, but feel free to customize to your heart's content.
45  # These two settings work together to allow you to limit a spec run
46  # to individual examples or groups you care about by tagging them with
47  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
48  # get run.
49  config.filter_run :focus
50  config.run_all_when_everything_filtered = true
51
52  # Limits the available syntax to the non-monkey patched syntax that is recommended.
53  # For more details, see:
54  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
55  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
56  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
57  #config.disable_monkey_patching!
58
59  # Many RSpec users commonly either run the entire suite or an individual
60  # file, and it's useful to allow more verbose output when running an
61  # individual spec file.
62  if config.files_to_run.one?
63    # Use the documentation formatter for detailed output,
64    # unless a formatter has already been configured
65    # (e.g. via a command-line flag).
66    config.default_formatter = 'doc'
67  end
68
69  # Print the 10 slowest examples and example groups at the
70  # end of the spec run, to help surface which specs are running
71  # particularly slow.
72  #config.profile_examples = 10
73
74  # Run specs in random order to surface order dependencies. If you find an
75  # order dependency and want to debug it, you can fix the order by providing
76  # the seed, which is printed after each run.
77  #     --seed 1234
78  config.order = :random
79
80  # Seed global randomization in this process using the `--seed` CLI option.
81  # Setting this allows you to use `--seed` to deterministically reproduce
82  # test failures related to randomization by passing the same `--seed` value
83  # as the one that triggered the failure.
84  Kernel.srand config.seed
85end