|
40 | 40 | mocks.verify_partial_doubles = true |
41 | 41 | end |
42 | 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 | | -=begin |
| 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 | + |
46 | 46 | # These two settings work together to allow you to limit a spec run |
47 | 47 | # to individual examples or groups you care about by tagging them with |
48 | 48 | # `:focus` metadata. When nothing is tagged with `:focus`, all examples |
|
53 | 53 | # Allows RSpec to persist some state between runs in order to support |
54 | 54 | # the `--only-failures` and `--next-failure` CLI options. We recommend |
55 | 55 | # you configure your source control system to ignore this file. |
56 | | - config.example_status_persistence_file_path = "spec/examples.txt" |
| 56 | + # config.example_status_persistence_file_path = "spec/examples.txt" |
57 | 57 |
|
58 | 58 | # Limits the available syntax to the non-monkey patched syntax that is |
59 | 59 | # recommended. For more details, see: |
|
79 | 79 | # Print the 10 slowest examples and example groups at the |
80 | 80 | # end of the spec run, to help surface which specs are running |
81 | 81 | # particularly slow. |
82 | | - config.profile_examples = 10 |
| 82 | + # config.profile_examples = 10 |
83 | 83 |
|
84 | 84 | # Run specs in random order to surface order dependencies. If you find an |
85 | 85 | # order dependency and want to debug it, you can fix the order by providing |
|
92 | 92 | # test failures related to randomization by passing the same `--seed` value |
93 | 93 | # as the one that triggered the failure. |
94 | 94 | Kernel.srand config.seed |
95 | | -=end |
96 | 95 | end |
0 commit comments