|
43 | 43 | add_filter '/public/' |
44 | 44 | add_filter '/deploy/' |
45 | 45 | add_filter '/spec/' # for rspec |
| 46 | + |
| 47 | + # Additional coverage groups |
| 48 | + add_group 'Policies', 'app/policies' |
| 49 | + add_group 'Builders', 'app/builders' |
| 50 | + add_group 'Resources', 'app/resource' |
| 51 | + add_group 'Robots', 'app/robots' |
| 52 | + add_group 'Forms', 'app/forms' |
| 53 | + add_group 'Sanitizers', 'app/sanitizers' |
| 54 | + add_group 'Notifiers', 'app/notifiers' |
46 | 55 | end |
47 | 56 |
|
48 | 57 | RSpec.configure do |config| |
|
86 | 95 | # # is tagged with `:focus`, all examples get run. RSpec also provides |
87 | 96 | # # aliases for `it`, `describe`, and `context` that include `:focus` |
88 | 97 | # # metadata: `fit`, `fdescribe` and `fcontext`, respectively. |
89 | | - # config.filter_run_when_matching :focus |
| 98 | + # # config.filter_run_when_matching :focus |
90 | 99 | # |
91 | 100 | # # Allows RSpec to persist some state between runs in order to support |
92 | 101 | # # the `--only-failures` and `--next-failure` CLI options. We recommend |
93 | 102 | # # you configure your source control system to ignore this file. |
94 | | - # config.example_status_persistence_file_path = "spec/examples.txt" |
| 103 | + # # config.example_status_persistence_file_path = "spec/examples.txt" |
95 | 104 | # |
96 | 105 | # # Limits the available syntax to the non-monkey patched syntax that is |
97 | 106 | # # recommended. For more details, see: |
98 | 107 | # # - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/ |
99 | 108 | # # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/ |
100 | | - # # - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode |
101 | | - # config.disable_monkey_patching! |
| 109 | + # # - http://www.rubydoc.info/gems/rspec-core/RSpec/Core/Configuration |
| 110 | + # # config.disable_monkey_patching! |
102 | 111 | # |
103 | 112 | # # Many RSpec users commonly either run the entire suite or an individual |
104 | 113 | # # file, and it's useful to allow more verbose output when running an |
105 | 114 | # # individual spec file. |
106 | | - # if config.files_to_run.one? |
107 | | - # # Use the documentation formatter for detailed output, |
108 | | - # # unless a formatter has already been configured |
109 | | - # # (e.g. via a command-line flag). |
110 | | - # config.default_formatter = "doc" |
111 | | - # end |
| 115 | + # # if config.files_to_run.one? |
| 116 | + # # # Use the documentation formatter for detailed output, |
| 117 | + # # # unless a formatter has already been configured |
| 118 | + # # # (e.g. via a command-line flag). |
| 119 | + # # config.default_formatter = "doc" |
| 120 | + # # end |
112 | 121 | # |
113 | 122 | # # Print the 10 slowest examples and example groups at the |
114 | 123 | # # end of the spec run, to help surface which specs are running |
115 | 124 | # # particularly slow. |
116 | | - # config.profile_examples = 10 |
| 125 | + config.profile_examples = 5 |
117 | 126 | # |
118 | 127 | # # Run specs in random order to surface order dependencies. If you find an |
119 | 128 | # # order dependency and want to debug it, you can fix the order by providing |
120 | 129 | # # the seed, which is printed after each run. |
121 | 130 | # # --seed 1234 |
122 | | - # config.order = :random |
| 131 | + config.order = :random |
123 | 132 | # |
124 | 133 | # # Seed global randomization in this process using the `--seed` CLI option. |
125 | 134 | # # Setting this allows you to use `--seed` to deterministically reproduce |
126 | 135 | # # test failures related to randomization by passing the same `--seed` value |
127 | 136 | # # as the one that triggered the failure. |
128 | | - # Kernel.srand config.seed |
| 137 | + # # Kernel.srand config.seed |
129 | 138 | end |
0 commit comments