|
4 | 4 |
|
5 | 5 | require "libdatadog" |
6 | 6 |
|
| 7 | +# This file was generated by the `rspec --init` command + manually tweaked. |
| 8 | +# |
| 9 | +# See https://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration |
7 | 10 | RSpec.configure do |config| |
8 | | - # Enable flags like --only-failures and --next-failure |
| 11 | + config.expect_with :rspec do |expectations| |
| 12 | + # This option will default to `true` in RSpec 4. |
| 13 | + expectations.include_chain_clauses_in_custom_matcher_descriptions = true |
| 14 | + end |
| 15 | + |
| 16 | + config.mock_with :rspec do |mocks| |
| 17 | + # This will default to `true` in RSpec 4. |
| 18 | + mocks.verify_partial_doubles = true |
| 19 | + end |
| 20 | + |
| 21 | + # This option will default to `:apply_to_host_groups` in RSpec 4. |
| 22 | + config.shared_context_metadata_behavior = :apply_to_host_groups |
| 23 | + |
| 24 | + # This allows you to limit a spec run to individual examples or groups |
| 25 | + # you care about by tagging them with `:focus` metadata. When nothing |
| 26 | + # is tagged with `:focus`, all examples get run. RSpec also provides |
| 27 | + # aliases for `it`, `describe`, and `context` that include `:focus` |
| 28 | + # metadata: `fit`, `fdescribe` and `fcontext`, respectively. |
| 29 | + config.filter_run_when_matching :focus |
| 30 | + |
| 31 | + # Allows RSpec to persist some state between runs in order to support |
| 32 | + # the `--only-failures` and `--next-failure` CLI options. We recommend |
| 33 | + # you configure your source control system to ignore this file. |
9 | 34 | config.example_status_persistence_file_path = ".rspec_status" |
10 | 35 |
|
11 | 36 | # Disable RSpec exposing methods globally on `Module` and `main` |
12 | 37 | config.disable_monkey_patching! |
13 | 38 |
|
14 | | - config.expect_with :rspec do |c| |
15 | | - c.syntax = :expect |
| 39 | + # This setting enables warnings. It's recommended, but in some cases may |
| 40 | + # be too noisy due to issues in dependencies. |
| 41 | + config.warnings = true |
| 42 | + |
| 43 | + # Many RSpec users commonly either run the entire suite or an individual |
| 44 | + # file, and it's useful to allow more verbose output when running an |
| 45 | + # individual spec file. |
| 46 | + if config.files_to_run.one? |
| 47 | + # Use the documentation formatter for detailed output, |
| 48 | + # unless a formatter has already been configured |
| 49 | + # (e.g. via a command-line flag). |
| 50 | + config.default_formatter = "doc" |
16 | 51 | end |
| 52 | + |
| 53 | + # Print the 10 slowest examples and example groups at the |
| 54 | + # end of the spec run, to help surface which specs are running |
| 55 | + # particularly slow. |
| 56 | + config.profile_examples = 10 |
| 57 | + |
| 58 | + # Run specs in random order to surface order dependencies. If you find an |
| 59 | + # order dependency and want to debug it, you can fix the order by providing |
| 60 | + # the seed, which is printed after each run. |
| 61 | + # --seed 1234 |
| 62 | + config.order = :random |
| 63 | + |
| 64 | + # Seed global randomization in this process using the `--seed` CLI option. |
| 65 | + # Setting this allows you to use `--seed` to deterministically reproduce |
| 66 | + # test failures related to randomization by passing the same `--seed` value |
| 67 | + # as the one that triggered the failure. |
| 68 | + Kernel.srand config.seed |
17 | 69 | end |
0 commit comments