|
| 1 | +# frozen_string_literal: true |
| 2 | + |
1 | 3 | # This file was generated by the `rspec --init` command. Conventionally, all |
2 | 4 | # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`. |
3 | 5 | # The generated `.rspec` file contains `--require spec_helper` which will cause |
|
44 | 46 | # triggering implicit auto-inclusion in groups with matching metadata. |
45 | 47 | config.shared_context_metadata_behavior = :apply_to_host_groups |
46 | 48 |
|
47 | | -# The settings below are suggested to provide a good initial experience |
48 | | -# with RSpec, but feel free to customize to your heart's content. |
49 | | -=begin |
50 | | - # This allows you to limit a spec run to individual examples or groups |
51 | | - # you care about by tagging them with `:focus` metadata. When nothing |
52 | | - # is tagged with `:focus`, all examples get run. RSpec also provides |
53 | | - # aliases for `it`, `describe`, and `context` that include `:focus` |
54 | | - # metadata: `fit`, `fdescribe` and `fcontext`, respectively. |
55 | | - config.filter_run_when_matching :focus |
56 | | -
|
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 | | -
|
62 | | - # Limits the available syntax to the non-monkey patched syntax that is |
63 | | - # recommended. For more details, see: |
64 | | - # - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/ |
65 | | - # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/ |
66 | | - # - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode |
67 | | - config.disable_monkey_patching! |
68 | | -
|
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 | | -
|
73 | | - # Many RSpec users commonly either run the entire suite or an individual |
74 | | - # file, and it's useful to allow more verbose output when running an |
75 | | - # individual spec file. |
76 | | - if config.files_to_run.one? |
77 | | - # Use the documentation formatter for detailed output, |
78 | | - # unless a formatter has already been configured |
79 | | - # (e.g. via a command-line flag). |
80 | | - config.default_formatter = "doc" |
81 | | - end |
82 | | -
|
83 | | - # Print the 10 slowest examples and example groups at the |
84 | | - # end of the spec run, to help surface which specs are running |
85 | | - # particularly slow. |
86 | | - config.profile_examples = 10 |
87 | | -
|
88 | | - # Run specs in random order to surface order dependencies. If you find an |
89 | | - # order dependency and want to debug it, you can fix the order by providing |
90 | | - # the seed, which is printed after each run. |
91 | | - # --seed 1234 |
92 | | - config.order = :random |
93 | | -
|
94 | | - # Seed global randomization in this process using the `--seed` CLI option. |
95 | | - # Setting this allows you to use `--seed` to deterministically reproduce |
96 | | - # test failures related to randomization by passing the same `--seed` value |
97 | | - # as the one that triggered the failure. |
98 | | - Kernel.srand config.seed |
99 | | -=end |
| 49 | + # The settings below are suggested to provide a good initial experience |
| 50 | + # with RSpec, but feel free to customize to your heart's content. |
| 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 | + # |
| 58 | + # # Allows RSpec to persist some state between runs in order to support |
| 59 | + # # the `--only-failures` and `--next-failure` CLI options. We recommend |
| 60 | + # # you configure your source control system to ignore this file. |
| 61 | + # config.example_status_persistence_file_path = "spec/examples.txt" |
| 62 | + # |
| 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 | + # |
| 70 | + # # This setting enables warnings. It's recommended, but in some cases may |
| 71 | + # # be too noisy due to issues in dependencies. |
| 72 | + # config.warnings = true |
| 73 | + # |
| 74 | + # # Many RSpec users commonly either run the entire suite or an individual |
| 75 | + # # file, and it's useful to allow more verbose output when running an |
| 76 | + # # individual spec file. |
| 77 | + # if config.files_to_run.one? |
| 78 | + # # Use the documentation formatter for detailed output, |
| 79 | + # # unless a formatter has already been configured |
| 80 | + # # (e.g. via a command-line flag). |
| 81 | + # config.default_formatter = "doc" |
| 82 | + # end |
| 83 | + # |
| 84 | + # # Print the 10 slowest examples and example groups at the |
| 85 | + # # end of the spec run, to help surface which specs are running |
| 86 | + # # particularly slow. |
| 87 | + # config.profile_examples = 10 |
| 88 | + # |
| 89 | + # # Run specs in random order to surface order dependencies. If you find an |
| 90 | + # # order dependency and want to debug it, you can fix the order by providing |
| 91 | + # # the seed, which is printed after each run. |
| 92 | + # # --seed 1234 |
| 93 | + # config.order = :random |
| 94 | + # |
| 95 | + # # Seed global randomization in this process using the `--seed` CLI option. |
| 96 | + # # Setting this allows you to use `--seed` to deterministically reproduce |
| 97 | + # # test failures related to randomization by passing the same `--seed` value |
| 98 | + # # as the one that triggered the failure. |
| 99 | + # Kernel.srand config.seed |
100 | 100 | end |
0 commit comments