@@ -3,14 +3,14 @@ Feature: `have_http_status` matcher
3
3
The `have_http_status` matcher is used to specify that a response returns a
4
4
desired status code. It accepts one argument in any of the following formats:
5
5
6
- * numeric
7
- * name ( defined in `Rack::Utils::SYMBOL_TO_STATUS_CODE`)
8
- * `ActionDispatch::TestResponse` alias (`:success`, `:missing`, `:redirect`, or `:error`)
6
+ * numeric code
7
+ * status name as defined in `Rack::Utils::SYMBOL_TO_STATUS_CODE`
8
+ * generic status type (`:success`, `:missing`, `:redirect`, or `:error`)
9
9
10
10
The matcher works on any `response` object. It is available for use in
11
11
[controller specs](../controller-specs), [request specs](../request-specs), and [feature specs](../feature-specs).
12
12
13
- Scenario : Checking a numeric response code
13
+ Scenario : Checking a numeric status code
14
14
Given a file named "spec/controllers/application_controller_spec.rb" with:
15
15
"""ruby
16
16
require "rails_helper"
@@ -35,7 +35,7 @@ Feature: `have_http_status` matcher
35
35
When I run `rspec spec`
36
36
Then the examples should all pass
37
37
38
- Scenario : Checking a symbolic response code (by name)
38
+ Scenario : Checking a symbolic status name
39
39
Given a file named "spec/controllers/application_controller_spec.rb" with:
40
40
"""ruby
41
41
require "rails_helper"
@@ -60,7 +60,7 @@ Feature: `have_http_status` matcher
60
60
When I run `rspec spec`
61
61
Then the examples should all pass
62
62
63
- Scenario : Checking a symbolic response code (by `ActionDispatch::TestRespose` alias)
63
+ Scenario : Checking a symbolic generic status type
64
64
Given a file named "spec/controllers/application_controller_spec.rb" with:
65
65
"""ruby
66
66
require "rails_helper"
0 commit comments