@@ -111,6 +111,9 @@ $ bundle exec rspec spec/controllers/accounts_controller_spec.rb
111
111
112
112
# Run a single example from a spec file (by line number)
113
113
$ bundle exec rspec spec/controllers/accounts_controller_spec.rb:8
114
+
115
+ # See all options for running specs
116
+ $ bundle exec rspec --help
114
117
```
115
118
116
119
## RSpec DSL Basics (or, how do I write a spec?)
@@ -234,8 +237,6 @@ or for official Rails API documentation on the given `TestCase` class.
234
237
> RSpec Rails provides thoughtfully selected features
235
238
> to encourage good testing practices, but there’s no “right” way to do it.
236
239
> Ultimately, it’s up to you to decide how your test suite will be composed.
237
- >
238
- > (You may even define custom types, or write specs with no type at all.)
239
240
240
241
[ request ] : https://relishapp.com/rspec/rspec-rails/docs/request-specs/request-spec
241
242
[ feature ] : https://www.relishapp.com/rspec/rspec-rails/docs/feature-specs/feature-spec
@@ -253,7 +254,7 @@ or for official Rails API documentation on the given `TestCase` class.
253
254
254
255
### I’m writing a spec file from scratch. How do I assign it a type?
255
256
256
- Simply place the spec in the appropriate folder
257
+ Simply place the spec [ in the appropriate folder] [ ]
257
258
(_ e.g.,_ ` spec/models/ ` for model specs)
258
259
and RSpec will set its type automatically.
259
260
@@ -267,7 +268,7 @@ RSpec.describe User, type: :model do
267
268
...
268
269
```
269
270
270
- [ modified the default `rails_helper.rb` configuration ] : https://relishapp.com/rspec/rspec-rails/docs/upgrade#file-type-inference-disabled
271
+ [ in the appropriate folder ] : https://relishapp.com/rspec/rspec-rails/docs/directory-structure
271
272
272
273
### System specs, feature specs, request specs–what’s the difference?
273
274
0 commit comments