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# The `.rspec` file also contains a few flags that are not defaults but that
16# users commonly want.
17
18require 'benchmark'
19Dir['lib/**/**/*.rb'].each do |file|
20  require File.expand_path(file)
21end
22
23# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
24RSpec.configure do |config|
25  # rspec-expectations config goes here. You can use an alternate
26  # assertion/expectation library such as wrong or the stdlib/minitest
27  # assertions if you prefer.
28  config.expect_with :rspec do |expectations|
29    # This option will default to `true` in RSpec 4. It makes the `description`
30    # and `failure_message` of custom matchers include text for helper methods
31    # defined using `chain`, e.g.:
32    #     be_bigger_than(2).and_smaller_than(4).description
33    #     # => "be bigger than 2 and smaller than 4"
34    # ...rather than:
35    #     # => "be bigger than 2"
36    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
37  end
38
39  # rspec-mocks config goes here. You can use an alternate test double
40  # library (such as bogus or mocha) by changing the `mock_with` option here.
41  config.mock_with :rspec do |mocks|
42    # Prevents you from mocking or stubbing a method that does not exist on
43    # a real object. This is generally recommended, and will default to
44    # `true` in RSpec 4.
45    mocks.verify_partial_doubles = true
46  end
47
48# The settings below are suggested to provide a good initial experience
49# with RSpec, but feel free to customize to your heart's content.
50=begin
51  # These two settings work together to allow you to limit a spec run
52  # to individual examples or groups you care about by tagging them with
53  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
54  # get run.
55  config.filter_run :focus
56  config.run_all_when_everything_filtered = true
57
58  # Limits the available syntax to the non-monkey patched syntax that is
59  # recommended. For more details, see:
60  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
61  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
62  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
63  config.disable_monkey_patching!
64
65  # This setting enables warnings. It's recommended, but in some cases may
66  # be too noisy due to issues in dependencies.
67  config.warnings = true
68
69  # Many RSpec users commonly either run the entire suite or an individual
70  # file, and it's useful to allow more verbose output when running an
71  # individual spec file.
72  if config.files_to_run.one?
73    # Use the documentation formatter for detailed output,
74    # unless a formatter has already been configured
75    # (e.g. via a command-line flag).
76    config.default_formatter = 'doc'
77  end
78
79  # Print the 10 slowest examples and example groups at the
80  # end of the spec run, to help surface which specs are running
81  # particularly slow.
82  config.profile_examples = 10
83
84  # Run specs in random order to surface order dependencies. If you find an
85  # order dependency and want to debug it, you can fix the order by providing
86  # the seed, which is printed after each run.
87  #     --seed 1234
88  config.order = :random
89
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
96end