bugsnag 6.12.1 → 6.15.0

data/features/rails_features/release_stage.feature

@@ -1,89 +1,27 @@
 Feature: Release stage
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Release_stage should default to RAILS_ENV
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "RAILS_ENV" to "rails_env"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/release_stage/default" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Release_stage should default to RAILS_ENV
+  Given I set environment variable "RAILS_ENV" to "rails_env"
+  And I start the rails service
+  When I navigate to the route "/release_stage/default" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "app.releaseStage" equals "rails_env"
 
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Release_stage can be set in an initializer
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_RELEASE_STAGE" to "maze_release_stage_env"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/release_stage/default" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Release_stage can be set in an initializer
+  Given I set environment variable "BUGSNAG_RELEASE_STAGE" to "maze_release_stage_env"
+  And I start the rails service
+  When I navigate to the route "/release_stage/default" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "app.releaseStage" equals "maze_release_stage_env"
 
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Release_stage can be set after an initializer
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/release_stage/after?stage=set_after_env" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Release_stage can be set after an initializer
+  Given I start the rails service
+  When I navigate to the route "/release_stage/after?stage=set_after_env" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "app.releaseStage" equals "set_after_env"
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |

data/features/rails_features/send_code.feature

@@ -1,60 +1,18 @@
 Feature: Send code
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Send_code can be updated in an initializer
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_SEND_CODE" to "false"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/send_code/initializer" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Send_code can be updated in an initializer
+  Given I set environment variable "BUGSNAG_SEND_CODE" to "false"
+  And I start the rails service
+  When I navigate to the route "/send_code/initializer" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "exceptions.0.stacktrace.0.code" is null
 
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Send_code can be updated after an initializer
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/send_code/after" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Send_code can be updated after an initializer
+  Given I start the rails service
+  When I navigate to the route "/send_code/after" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "exceptions.0.stacktrace.0.code" is null
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |

data/features/rails_features/send_environment.feature

@@ -1,39 +1,13 @@
 Feature: Send environment
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Send_environment should send environment in handled errors when true
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_SEND_ENVIRONMENT" to "true"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/send_environment/initializer" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Send_environment should send environment in handled errors when true
+  Given I set environment variable "BUGSNAG_SEND_ENVIRONMENT" to "true"
+  And I start the rails service
+  When I navigate to the route "/send_environment/initializer" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the exception "errorClass" equals "RuntimeError"
   And the exception "message" starts with "handled string"
   And the event "metaData.environment.REQUEST_METHOD" equals "GET"
-  And the event "metaData.environment.railsVersion" is not null
   And the event "app.type" equals "rails"
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |

data/features/rails_features/unhandled.feature

@@ -1,20 +1,11 @@
 Feature: Unhandled exceptions support
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Unhandled RuntimeError
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/unhandled/error" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@rails3 @rails4 @rails5 @rails6
+Scenario: Unhandled RuntimeError
+  Given I start the rails service
+  When I navigate to the route "/unhandled/error" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "unhandled" is true
   And the exception "errorClass" equals "NameError"
   And the exception "message" starts with "undefined local variable or method `generate_unhandled_error' for #<UnhandledController"
@@ -23,19 +14,3 @@ Scenario Outline: Unhandled RuntimeError
   And the event "severity" equals "error"
   And the event "severityReason.type" equals "unhandledExceptionMiddleware"
   And the event "severityReason.attributes.framework" equals "Rack"
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |

data/features/rails_features/user_info.feature

@@ -1,90 +1,52 @@
 Feature: Capture user information
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
+@rails3
 Scenario Outline: Warden user information is sent
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/warden/create" on port "6128<rails_version>"
-  And I navigate to the route "/warden/<route>?email=testtest@test.test" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+  Given I start the rails service
+  When I navigate to the route "/warden/create" on the rails app
+  And I navigate to the route "/warden/<route>?email=testtest@test.test" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "user.email" equals "testtest@test.test"
   And the event "user.name" equals "Warden User"
   And the event "user.first_name" equals "Warden"
   And the event "user.last_name" equals "User"
 
   Examples:
-    | ruby_version | rails_version | route     |
-    | 2.0          | 3             | handled   |
-    | 2.0          | 3             | unhandled |
-    | 2.1          | 3             | handled   |
-    | 2.1          | 3             | unhandled |
-    | 2.2          | 3             | handled   |
-    | 2.2          | 3             | unhandled |
-    | 2.3          | 3             | handled   |
-    | 2.3          | 3             | unhandled |
-    | 2.4          | 3             | handled   |
-    | 2.4          | 3             | unhandled |
-    | 2.5          | 3             | handled   |
-    | 2.5          | 3             | unhandled |
-
+    | route     |
+    | handled   |
+    | unhandled |
 
+@rails4
 Scenario Outline: Devise user information is sent
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/devise/create" on port "6128<rails_version>"
-  And I navigate to the route "/devise/<route>" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+  Given I start the rails service
+  When I navigate to the route "/devise/create" on the rails app
+  And I navigate to the route "/devise/<route>" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "user.email" equals "test+test@test.test"
   And the event "user.name" equals "Devise User"
   And the event "user.first_name" equals "Devise"
   And the event "user.last_name" equals "User"
 
   Examples:
-    | ruby_version | rails_version | route     |
-    | 2.2          | 4             | handled   |
-    | 2.2          | 4             | unhandled |
-    | 2.3          | 4             | handled   |
-    | 2.3          | 4             | unhandled |
+    | route     |
+    | handled   |
+    | unhandled |
 
+@rails5 @rails6
 Scenario Outline: Clearance user information is sent
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/clearance/create" on port "6128<rails_version>"
-  And I navigate to the route "/clearance/<route>" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+  Given I start the rails service
+  When I navigate to the route "/clearance/create" on the rails app
+  And I navigate to the route "/clearance/<route>" on the rails app
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "user.email" equals "testtest@test.test"
   And the event "user.name" equals "Clearance User"
   And the event "user.first_name" equals "Clearance"
   And the event "user.last_name" equals "User"
 
   Examples:
-    | ruby_version | rails_version | route     |
-    | 2.2          | 5             | handled   |
-    | 2.2          | 5             | unhandled |
-    | 2.3          | 5             | handled   |
-    | 2.3          | 5             | unhandled |
-    | 2.4          | 5             | handled   |
-    | 2.4          | 5             | unhandled |
-    | 2.5          | 5             | handled   |
-    | 2.5          | 5             | unhandled |
-    | 2.5          | 6             | handled   |
-    | 2.5          | 6             | unhandled |
+    | route     |
+    | handled   |
+    | unhandled |

data/features/sidekiq.feature

@@ -1,97 +1,30 @@
 Feature: Bugsnag raises errors in Sidekiq workers
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: An unhandled RuntimeError sends a report
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "SIDEKIQ_VERSION" to "<sidekiq_version>"
-  And I start the service "sidekiq"
-  And I run the command "bundle exec ruby initializers/UnhandledError.rb" on the service "sidekiq"
-  And I wait for 1 seconds
-  Then I should receive a request
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request used payload v4 headers
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+Scenario: An unhandled RuntimeError sends a report
+  Given I run the service "sidekiq" with the command "bundle exec rake sidekiq_tests:unhandled_error"
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "unhandled" is true
   And the event "severity" equals "error"
   And the event "context" equals "UnhandledError@default"
   And the event "severityReason.type" equals "unhandledExceptionMiddleware"
   And the event "severityReason.attributes.framework" equals "Sidekiq"
   And the exception "errorClass" equals "RuntimeError"
-  And the "file" of stack frame 0 equals "/usr/src/app.rb"
+  And the "file" of stack frame 0 equals "/app/app.rb"
   And the "lineNumber" of stack frame 0 equals 33
-  And the payload field "events.0.metaData.sidekiq" matches the JSON fixture in "features/fixtures/sidekiq/payloads/unhandled_metadata_ca_<created_at_present>.json"
+  And the payload field "events.0.metaData.sidekiq" matches the appropriate Sidekiq unhandled payload
   And the event "metaData.sidekiq.msg.created_at" is a parsable timestamp in seconds
   And the event "metaData.sidekiq.msg.enqueued_at" is a parsable timestamp in seconds
 
-  Examples:
-  | ruby version | sidekiq_version | created_at_present |
-  | 1.9.3        | ~> 2            | false              |
-  | 2.0          | ~> 2            | false              |
-  | 2.0          | ~> 3            | true               |
-  | 2.1          | ~> 2            | false              |
-  | 2.1          | ~> 3            | true               |
-  | 2.2          | ~> 2            | false              |
-  | 2.2          | ~> 3            | true               |
-  | 2.2          | ~> 4            | true               |
-  | 2.2          | ~> 5            | true               |
-  | 2.3          | ~> 2            | false              |
-  | 2.3          | ~> 3            | true               |
-  | 2.3          | ~> 4            | true               |
-  | 2.3          | ~> 5            | true               |
-  | 2.4          | ~> 2            | false              |
-  | 2.4          | ~> 3            | true               |
-  | 2.4          | ~> 4            | true               |
-  | 2.4          | ~> 5            | true               |
-  | 2.5          | ~> 2            | false              |
-  | 2.5          | ~> 3            | true               |
-  | 2.5          | ~> 4            | true               |
-  | 2.5          | ~> 5            | true               |
-
-Scenario Outline: A handled RuntimeError can be notified
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "SIDEKIQ_VERSION" to "<sidekiq_version>"
-  And I start the service "sidekiq"
-  And I run the command "bundle exec ruby initializers/HandledError.rb" on the service "sidekiq"
-  And I wait for 1 seconds
-  Then I should receive a request
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request used payload v4 headers
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+Scenario: A handled RuntimeError can be notified
+  Given I run the service "sidekiq" with the command "bundle exec rake sidekiq_tests:handled_error"
+  And I wait to receive a request
+  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
   And the event "unhandled" is false
   And the event "context" equals "HandledError@default"
   And the event "severity" equals "warning"
   And the event "severityReason.type" equals "handledException"
   And the exception "errorClass" equals "RuntimeError"
-  And the "file" of stack frame 0 equals "/usr/src/app.rb"
-  And the "lineNumber" of stack frame 0 equals 24
-  And the payload field "events.0.metaData.sidekiq" matches the JSON fixture in "features/fixtures/sidekiq/payloads/handled_metadata_ca_<created_at_present>.json"
+  And the payload field "events.0.metaData.sidekiq" matches the appropriate Sidekiq handled payload
   And the event "metaData.sidekiq.msg.created_at" is a parsable timestamp in seconds
-  And the event "metaData.sidekiq.msg.enqueued_at" is a parsable timestamp in seconds
-
-  Examples:
-  | ruby version | sidekiq_version | created_at_present |
-  | 1.9.3        | ~> 2            | false              |
-  | 2.0          | ~> 2            | false              |
-  | 2.0          | ~> 3            | true               |
-  | 2.1          | ~> 2            | false              |
-  | 2.1          | ~> 3            | true               |
-  | 2.2          | ~> 2            | false              |
-  | 2.2          | ~> 3            | true               |
-  | 2.2          | ~> 4            | true               |
-  | 2.2          | ~> 5            | true               |
-  | 2.3          | ~> 2            | false              |
-  | 2.3          | ~> 3            | true               |
-  | 2.3          | ~> 4            | true               |
-  | 2.3          | ~> 5            | true               |
-  | 2.4          | ~> 2            | false              |
-  | 2.4          | ~> 3            | true               |
-  | 2.4          | ~> 4            | true               |
-  | 2.4          | ~> 5            | true               |
-  | 2.5          | ~> 2            | false              |
-  | 2.5          | ~> 3            | true               |
-  | 2.5          | ~> 4            | true               |
-  | 2.5          | ~> 5            | true               |
+  And the event "metaData.sidekiq.msg.enqueued_at" is a parsable timestamp in seconds