|
1 | 1 | # This file was generated by the `rspec --init` command. Conventionally, all |
2 | 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 this |
4 | | -# file to always be loaded, without a need to explicitly require it in any files. |
| 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. |
5 | 6 | # |
6 | 7 | # Given that it is always loaded, you are encouraged to keep this file as |
7 | 8 | # light-weight as possible. Requiring heavyweight dependencies from this file |
8 | 9 | # will add to the boot time of your test suite on EVERY test run, even for an |
9 | 10 | # individual file that may not need all of that loaded. Instead, consider making |
10 | 11 | # a separate helper file that requires the additional dependencies and performs |
11 | | -# the additional setup, and require it from the spec files that actually need it. |
| 12 | +# the additional setup, and require it from the spec files that actually need |
| 13 | +# it. |
12 | 14 | # |
13 | 15 | # The `.rspec` file also contains a few flags that are not defaults but that |
14 | 16 | # users commonly want. |
|
30 | 32 | # This option will default to `true` in RSpec 4. It makes the `description` |
31 | 33 | # and `failure_message` of custom matchers include text for helper methods |
32 | 34 | # defined using `chain`, e.g.: |
33 | | - # be_bigger_than(2).and_smaller_than(4).description |
34 | | - # # => "be bigger than 2 and smaller than 4" |
| 35 | + # be_bigger_than(2).and_smaller_than(4).description |
| 36 | + # # => "be bigger than 2 and smaller than 4" |
35 | 37 | # ...rather than: |
36 | | - # # => "be bigger than 2" |
| 38 | + # # => "be bigger than 2" |
37 | 39 | expectations.include_chain_clauses_in_custom_matcher_descriptions = true |
38 | 40 | end |
39 | 41 |
|
|
56 | 58 | config.filter_run :focus |
57 | 59 | config.run_all_when_everything_filtered = true |
58 | 60 |
|
59 | | - # Limits the available syntax to the non-monkey patched syntax that is recommended. |
60 | | - # For more details, see: |
61 | | - # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax |
62 | | - # - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/ |
63 | | - # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching |
| 61 | + # Allows RSpec to persist some state between runs in order to support |
| 62 | + # the `--only-failures` and `--next-failure` CLI options. We recommend |
| 63 | + # you configure your source control system to ignore this file. |
| 64 | + config.example_status_persistence_file_path = "spec/examples.txt" |
| 65 | +
|
| 66 | + # Limits the available syntax to the non-monkey patched syntax that is |
| 67 | + # recommended. For more details, see: |
| 68 | + # - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/ |
| 69 | + # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/ |
| 70 | + # - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode |
64 | 71 | config.disable_monkey_patching! |
65 | 72 |
|
66 | 73 | # This setting enables warnings. It's recommended, but in some cases may |
|
0 commit comments