Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

file 254 lines (236 sloc) 11.967 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254
Feature: Install the Gem in a Rails application

Background:
Given I have built and installed the "hoptoad_notifier" gem

Scenario: Use the gem without vendoring the gem in a Rails application
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
Then the command should have run successfully
And I should receive a Hoptoad notification
And I should see the Rails version

Scenario: vendor the gem and uninstall
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I unpack the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
Then the command should have run successfully
When I uninstall the "hoptoad_notifier" gem
And I install cached gems
And I run "rake hoptoad:test"
Then I should see "** [Hoptoad] Success: Net::HTTPOK"
And I should receive two Hoptoad notifications

Scenario: Configure the notifier by hand
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure the notifier to use "myapikey" as an API key
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with ""
Then I should receive a Hoptoad notification

Scenario: Configuration within initializer isn't overridden by Railtie
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
Then the command should have run successfully
When I configure the notifier to use the following configuration lines:
"""
config.api_key = "myapikey"
config.project_root = "argle/bargle"
"""
And I define a response for "TestController#index":
"""
session[:value] = "test"
raise RuntimeError, "some message"
"""
And I route "/test/index" to "test#index"
And I perform a request to "http://example.com:123/test/index?param=value"
Then I should receive the following Hoptoad notification:
| project-root | argle/bargle |

Scenario: Try to install without an api key
When I generate a new Rails application
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with ""
Then I should see "Must pass --api-key or --heroku or create config/initializers/hoptoad.rb"

Scenario: Configure and deploy using only installed gem
When I generate a new Rails application
And I run "capify ."
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
And I run "cap -T"
Then I should see "deploy:notify_hoptoad"

Scenario: Configure and deploy using only vendored gem
When I generate a new Rails application
And I run "capify ."
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I unpack the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
And I uninstall the "hoptoad_notifier" gem
And I install cached gems
And I run "cap -T"
Then I should see "deploy:notify_hoptoad"

Scenario: Try to install when the hoptoad_notifier plugin still exists
When I generate a new Rails application
And I install the "hoptoad_notifier" plugin
And I configure the Hoptoad shim
And I configure the notifier to use "myapikey" as an API key
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with ""
Then I should see "You must first remove the hoptoad_notifier plugin. Please run: script/plugin remove hoptoad_notifier"

Scenario: Rescue an exception in a controller
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
And I define a response for "TestController#index":
"""
session[:value] = "test"
raise RuntimeError, "some message"
"""
And I route "/test/index" to "test#index"
And I perform a request to "http://example.com:123/test/index?param=value"
Then I should receive the following Hoptoad notification:
| component | test |
| action | index |
| error message | RuntimeError: some message |
| error class | RuntimeError |
| session | value: test |
| parameters | param: value |
| url | http://example.com:123/test/index?param=value |

Scenario: The gem should not be considered a framework gem
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
And I run "rake gems"
Then I should see that "hoptoad_notifier" is not considered a framework gem

Scenario: The app uses Vlad instead of Capistrano
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run "touch config/deploy.rb"
And I run "rm Capfile"
And I run the hoptoad generator with "-k myapikey"
Then "config/deploy.rb" should not contain "capistrano"

Scenario: Support the Heroku addon in the generator
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure the Heroku rake shim
And I configure the Heroku gem shim with "myapikey"
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "--heroku"
Then the command should have run successfully
And I should receive a Hoptoad notification
And I should see the Rails version
And my Hoptoad configuration should contain the following line:
"""
config.api_key = ENV['HOPTOAD_API_KEY']
"""

Scenario: Support the --app option for the Heroku addon in the generator
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure the Heroku rake shim
And I configure the Heroku gem shim with "myapikey" and multiple app support
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "--heroku -a myapp"
Then the command should have run successfully
And I should receive a Hoptoad notification
And I should see the Rails version
And my Hoptoad configuration should contain the following line:
"""
config.api_key = ENV['HOPTOAD_API_KEY']
"""

Scenario: Filtering parameters in a controller
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
When I configure the notifier to use the following configuration lines:
"""
config.api_key = "myapikey"
config.params_filters << "credit_card_number"
"""
And I define a response for "TestController#index":
"""
params[:credit_card_number] = "red23"
raise RuntimeError, "some message"
"""
And I route "/test/index" to "test#index"
And I perform a request to "http://example.com:123/test/index?param=value"
Then I should receive the following Hoptoad notification:
| component | test |
| action | index |
| error message | RuntimeError: some message |
| error class | RuntimeError |
| parameters | credit_card_number: [FILTERED] |
| url | http://example.com:123/test/index?param=value |

Scenario: Filtering session in a controller
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
When I configure the notifier to use the following configuration lines:
"""
config.api_key = "myapikey"
config.params_filters << "secret"
"""
And I define a response for "TestController#index":
"""
session["secret"] = "blue42"
raise RuntimeError, "some message"
"""
And I route "/test/index" to "test#index"
And I perform a request to "http://example.com:123/test/index?param=value"
Then I should receive the following Hoptoad notification:
| component | test |
| action | index |
| error message | RuntimeError: some message |
| error class | RuntimeError |
| session | secret: [FILTERED] |
| url | http://example.com:123/test/index?param=value |

Scenario: Filtering session and params based on Rails parameter filters
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
And I configure the application to filter parameter "secret"
And I define a response for "TestController#index":
"""
params["secret"] = "red23"
session["secret"] = "blue42"
raise RuntimeError, "some message"
"""
And I route "/test/index" to "test#index"
And I perform a request to "http://example.com:123/test/index?param=value"
Then I should receive the following Hoptoad notification:
| component | test |
| action | index |
| error message | RuntimeError: some message |
| error class | RuntimeError |
| params | secret: [FILTERED] |
| session | secret: [FILTERED] |
| url | http://example.com:123/test/index?param=value |

Scenario: Notify hoptoad within the controller
When I generate a new Rails application
And I configure the Hoptoad shim
And I configure my application to require the "hoptoad_notifier" gem
And I run the hoptoad generator with "-k myapikey"
And I define a response for "TestController#index":
"""
session[:value] = "test"
notify_hoptoad(RuntimeError.new("some message"))
render :nothing => true
"""
And I route "/test/index" to "test#index"
And I perform a request to "http://example.com:123/test/index?param=value"
Then I should receive the following Hoptoad notification:
| component | test |
| action | index |
| error message | RuntimeError: some message |
| error class | RuntimeError |
| session | value: test |
| parameters | param: value |
| url | http://example.com:123/test/index?param=value |
Something went wrong with that request. Please try again.