spec_helper.rb 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101
  1. # This file was generated by the `rails generate rspec:install` 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. #
  18. # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
  19. require 'webmock/rspec'
  20. RSpec.configure do |config|
  21. # rspec-expectations config goes here. You can use an alternate
  22. # assertion/expectation library such as wrong or the stdlib/minitest
  23. # assertions if you prefer.
  24. config.expect_with :rspec do |expectations|
  25. # This option will default to `true` in RSpec 4. It makes the `description`
  26. # and `failure_message` of custom matchers include text for helper methods
  27. # defined using `chain`, e.g.:
  28. # be_bigger_than(2).and_smaller_than(4).description
  29. # # => "be bigger than 2 and smaller than 4"
  30. # ...rather than:
  31. # # => "be bigger than 2"
  32. expectations.include_chain_clauses_in_custom_matcher_descriptions = true
  33. end
  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. # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
  43. # have no way to turn it off -- the option exists only for backwards
  44. # compatibility in RSpec 3). It causes shared context metadata to be
  45. # inherited by the metadata hash of host groups and examples, rather than
  46. # triggering implicit auto-inclusion in groups with matching metadata.
  47. config.shared_context_metadata_behavior = :apply_to_host_groups
  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. # This allows you to limit a spec run to individual examples or groups
  52. # you care about by tagging them with `:focus` metadata. When nothing
  53. # is tagged with `:focus`, all examples get run. RSpec also provides
  54. # aliases for `it`, `describe`, and `context` that include `:focus`
  55. # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
  56. config.filter_run_when_matching :focus
  57. # Allows RSpec to persist some state between runs in order to support
  58. # the `--only-failures` and `--next-failure` CLI options. We recommend
  59. # you configure your source control system to ignore this file.
  60. config.example_status_persistence_file_path = "spec/examples.txt"
  61. # Limits the available syntax to the non-monkey patched syntax that is
  62. # recommended. For more details, see:
  63. # - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
  64. # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
  65. # - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
  66. config.disable_monkey_patching!
  67. # Many RSpec users commonly either run the entire suite or an individual
  68. # file, and it's useful to allow more verbose output when running an
  69. # individual spec file.
  70. if config.files_to_run.one?
  71. # Use the documentation formatter for detailed output,
  72. # unless a formatter has already been configured
  73. # (e.g. via a command-line flag).
  74. config.default_formatter = 'doc'
  75. end
  76. # Print the 10 slowest examples and example groups at the
  77. # end of the spec run, to help surface which specs are running
  78. # particularly slow.
  79. config.profile_examples = 10
  80. # Run specs in random order to surface order dependencies. If you find an
  81. # order dependency and want to debug it, you can fix the order by providing
  82. # the seed, which is printed after each run.
  83. # --seed 1234
  84. config.order = :random
  85. # Seed global randomization in this process using the `--seed` CLI option.
  86. # Setting this allows you to use `--seed` to deterministically reproduce
  87. # test failures related to randomization by passing the same `--seed` value
  88. # as the one that triggered the failure.
  89. Kernel.srand config.seed
  90. =end
  91. end