features/rails.feature in airbrake-4.1.0 vs features/rails.feature in airbrake-4.2.0
- old
+ new
@@ -79,34 +79,34 @@
And I run `touch config/deploy.rb`
And I run `rm Capfile`
And I run `rails generate airbrake -k myapikey`
Then "config/deploy.rb" should not contain "capistrano"
- @wip
- Scenario: Support the Heroku addon in the generator
- When I configure the Airbrake shim
- And I run `rails generate airbrake -k myapikey -t`
- And I configure the Heroku shim with "myapikey"
- And I successfully run `rails generate airbrake --heroku`
- Then I should receive a Airbrake notification
- And I should see the Rails version
- And my Airbrake configuration should contain the following line:
- """
- config.api_key = ENV['HOPTOAD_API_KEY']
- """
+ # @wip
+ # Scenario: Support the Heroku addon in the generator
+ # When I configure the Airbrake shim
+ # And I run `rails generate airbrake -k myapikey -t`
+ # And I configure the Heroku shim with "myapikey"
+ # And I run `rails generate airbrake --heroku`
+ # Then I should receive a Airbrake notification
+ # And I should see the Rails version
+ # And my Airbrake configuration should contain the following line:
+ # """
+ # config.api_key = 'myapikey'
+ # """
- @wip
- Scenario: Support the --app option for the Heroku addon in the generator
- When I configure the Airbrake shim
- And I configure the Heroku shim with "myapikey" and multiple app support
- And I run `rails generate airbrake --heroku -a myapp -t`
- Then I should receive a Airbrake notification
- And I should see the Rails version
- And my Airbrake configuration should contain the following line:
- """
- config.api_key = ENV['HOPTOAD_API_KEY']
- """
+ # @wip
+ # Scenario: Support the --app option for the Heroku addon in the generator
+ # When I configure the Airbrake shim
+ # And I configure the Heroku shim with "myapikey" and multiple app support
+ # And I run `rails generate airbrake --heroku -a myapp -t`
+ # Then I should receive a Airbrake notification
+ # And I should see the Rails version
+ # And my Airbrake configuration should contain the following line:
+ # """
+ # config.api_key = 'myapikey'
+ # """
Scenario: Filtering parameters in a controller
When I configure the Airbrake shim
And I run `rails generate airbrake -k myapikey -t`
When I configure the notifier to use the following configuration lines:
@@ -162,9 +162,28 @@
"""
raise RuntimeError
"""
Then I should receive a Airbrake notification
And the Airbrake notification should not contain any of the sensitive Rack variables
+
+ Scenario: Filtering vs symbols
+ When I configure the Airbrake shim
+ And I run `rails generate airbrake -k myapikey -t`
+ When I configure the notifier to use the following configuration lines:
+ """
+ config.api_key = "myapikey"
+ config.logger = Logger.new STDOUT
+ """
+ And I configure the application to filter parameter "block"
+ And I define a response for "TestController#index":
+ """
+ request.env["foo"] = {:foo => "bar"}
+ raise RuntimeError, "some message"
+ """
+ And I route "/test/index" to "test#index"
+ And I perform a request to "http://example.com:123/test/index" in the "production" environment
+ Then I should receive a Airbrake notification
+ And the Airbrake notification should contain "some message"
Scenario: Notify airbrake within the controller
When I configure the Airbrake shim
And I run `rails generate airbrake -k myapikey -t`
And I define a response for "TestController#index":