bugsnag 6.12.1 → 6.15.0

data/features/plain_features/release_stages.feature

@@ -1,51 +1,20 @@
 Feature: Release stage configuration options
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Doesn't notify in the wrong release stage
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "BUGSNAG_NOTIFY_RELEASE_STAGE" to "stage_one"
+Scenario: Doesn't notify in the wrong release stage
+  Given I set environment variable "BUGSNAG_NOTIFY_RELEASE_STAGE" to "stage_one"
   And I set environment variable "BUGSNAG_RELEASE_STAGE" to "stage_two"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby configuration/send_unhandled.rb"
+  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/send_unhandled.rb"
   And I wait for 1 second
-  Then I should receive 0 requests
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
+  Then I should receive no requests
 
-Scenario Outline: Doesn't notify in the wrong release stage
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "BUGSNAG_NOTIFY_RELEASE_STAGE" to "stage_one"
+Scenario: Does notify in the correct release stage
+  Given I set environment variable "BUGSNAG_NOTIFY_RELEASE_STAGE" to "stage_one"
   And I set environment variable "BUGSNAG_RELEASE_STAGE" to "stage_one"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby configuration/send_unhandled.rb"
-  And I wait for 1 second
-  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"
+  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/send_unhandled.rb"
+  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 "severityReason.type" equals "unhandledException"
   And the exception "errorClass" equals "RuntimeError"
   And the "file" of stack frame 0 equals "/usr/src/app/configuration/send_unhandled.rb"
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |

data/features/plain_features/report_api_key.feature

@@ -1,40 +1,16 @@
 Feature: Plain report modify api key
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
 Scenario Outline: A report can have its api_key modified
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby report_modification/modify_api_key.rb"
-  And I wait for 1 second
-  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 "abcdefghijklmnopqrstuvwxyz123456"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/modify_api_key.rb"
+  And I wait to receive a request
+  Then the "Bugsnag-Api-Key" header equals "abcdefghijklmnopqrstuvwxyz123456"
+  And the payload field "apiKey" equals "abcdefghijklmnopqrstuvwxyz123456"
 
   Examples:
-  | ruby version | initiator               |
-  | 1.9.3        | handled_before_notify   |
-  | 1.9.3        | handled_block           |
-  | 1.9.3        | unhandled_before_notify |
-  | 2.0          | handled_before_notify   |
-  | 2.0          | handled_block           |
-  | 2.0          | unhandled_before_notify |
-  | 2.1          | handled_before_notify   |
-  | 2.1          | handled_block           |
-  | 2.1          | unhandled_before_notify |
-  | 2.2          | handled_before_notify   |
-  | 2.2          | handled_block           |
-  | 2.2          | unhandled_before_notify |
-  | 2.3          | handled_before_notify   |
-  | 2.3          | handled_block           |
-  | 2.3          | unhandled_before_notify |
-  | 2.4          | handled_before_notify   |
-  | 2.4          | handled_block           |
-  | 2.4          | unhandled_before_notify |
-  | 2.5          | handled_before_notify   |
-  | 2.5          | handled_block           |
-  | 2.5          | unhandled_before_notify |
+  | initiator               |
+  | handled_before_notify   |
+  | handled_block           |
+  | unhandled_before_notify |
+  | handled_on_error        |
+  | unhandled_on_error      |

data/features/plain_features/report_severity.feature

@@ -1,42 +1,17 @@
 Feature: Plain report modify severity
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
 Scenario Outline: A reports severity can be modified
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby report_modification/modify_severity.rb"
-  And I wait for 1 second
-  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"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/modify_severity.rb"
+  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 "severity" equals "info"
   And the event "severityReason.type" equals "userCallbackSetSeverity"
 
   Examples:
-  | ruby version | initiator               |
-  | 1.9.3        | handled_before_notify   |
-  | 1.9.3        | handled_block           |
-  | 1.9.3        | unhandled_before_notify |
-  | 2.0          | handled_before_notify   |
-  | 2.0          | handled_block           |
-  | 2.0          | unhandled_before_notify |
-  | 2.1          | handled_before_notify   |
-  | 2.1          | handled_block           |
-  | 2.1          | unhandled_before_notify |
-  | 2.2          | handled_before_notify   |
-  | 2.2          | handled_block           |
-  | 2.2          | unhandled_before_notify |
-  | 2.3          | handled_before_notify   |
-  | 2.3          | handled_block           |
-  | 2.3          | unhandled_before_notify |
-  | 2.4          | handled_before_notify   |
-  | 2.4          | handled_block           |
-  | 2.4          | unhandled_before_notify |
-  | 2.5          | handled_before_notify   |
-  | 2.5          | handled_block           |
-  | 2.5          | unhandled_before_notify |
+  | initiator               |
+  | handled_before_notify   |
+  | handled_block           |
+  | unhandled_before_notify |
+  | handled_on_error        |
+  | unhandled_on_error      |

data/features/plain_features/report_stack_frames.feature

@@ -1,72 +1,33 @@
 Feature: Plain report modify stack frames
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
 Scenario Outline: Stack frames can be removed
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/remove_stack_frame.rb"
-  And I wait for 1 second
-  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"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/remove_stack_frame.rb"
+  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 "file" of the top non-bugsnag stackframe equals "/usr/src/app/stack_frame_modification/initiators/<initiator>.rb"
   And the "lineNumber" of stack frame 0 equals <lineNumber>
 
   Examples:
-  | ruby version | initiator               | lineNumber |
-  | 1.9.3        | handled_before_notify   | 20         |
-  | 1.9.3        | unhandled_before_notify | 21         |
-  | 2.0          | handled_before_notify   | 20         |
-  | 2.0          | unhandled_before_notify | 21         |
-  | 2.1          | handled_before_notify   | 20         |
-  | 2.1          | unhandled_before_notify | 21         |
-  | 2.2          | handled_before_notify   | 20         |
-  | 2.2          | unhandled_before_notify | 21         |
-  | 2.3          | handled_before_notify   | 20         |
-  | 2.3          | unhandled_before_notify | 21         |
-  | 2.4          | handled_before_notify   | 20         |
-  | 2.4          | unhandled_before_notify | 21         |
-  | 2.5          | handled_before_notify   | 20         |
-  | 2.5          | unhandled_before_notify | 21         |
-
-Scenario Outline: Stack frames can be removed from a notified string
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "handled_block"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/remove_stack_frame.rb"
-  And I wait for 1 second
-  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"
+  | initiator               | lineNumber |
+  | handled_before_notify   | 20         |
+  | unhandled_before_notify | 21         |
+  | handled_on_error        | 20         |
+  | unhandled_on_error      | 21         |
+
+Scenario: Stack frames can be removed from a notified string
+  Given I set environment variable "CALLBACK_INITIATOR" to "handled_block"
+  When I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/remove_stack_frame.rb"
+  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 "file" of the top non-bugsnag stackframe equals "/usr/src/app/stack_frame_modification/initiators/handled_block.rb"
   And the "lineNumber" of the top non-bugsnag stackframe equals 19
 
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
 Scenario Outline: Stack frames can be marked as in project
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/mark_frames_in_project.rb"
-  And I wait for 1 second
-  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"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/mark_frames_in_project.rb"
+  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 "file" of stack frame 0 equals "/usr/src/app/stack_frame_modification/initiators/<initiator>.rb"
   And the event "exceptions.0.stacktrace.0.inProject" is null
   And the event "exceptions.0.stacktrace.1.inProject" is true
@@ -74,44 +35,19 @@ Scenario Outline: Stack frames can be marked as in project
   And the event "exceptions.0.stacktrace.3.inProject" is true
 
   Examples:
-  | ruby version | initiator               |
-  | 1.9.3        | handled_before_notify   |
-  | 1.9.3        | unhandled_before_notify |
-  | 2.0          | handled_before_notify   |
-  | 2.0          | unhandled_before_notify |
-  | 2.1          | handled_before_notify   |
-  | 2.1          | unhandled_before_notify |
-  | 2.2          | handled_before_notify   |
-  | 2.2          | unhandled_before_notify |
-  | 2.3          | handled_before_notify   |
-  | 2.3          | unhandled_before_notify |
-  | 2.4          | handled_before_notify   |
-  | 2.4          | unhandled_before_notify |
-  | 2.5          | handled_before_notify   |
-  | 2.5          | unhandled_before_notify |
-
-Scenario Outline: Stack frames can be marked as in project with a handled string
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "handled_block"
-  And I have built the service "plain-ruby"
+  | initiator               |
+  | handled_before_notify   |
+  | unhandled_before_notify |
+  | handled_on_error        |
+  | unhandled_on_error      |
+
+Scenario: Stack frames can be marked as in project with a handled string
+  Given I set environment variable "CALLBACK_INITIATOR" to "handled_block"
   And I run the service "plain-ruby" with the command "bundle exec ruby stack_frame_modification/mark_frames_in_project.rb"
-  And I wait for 1 second
-  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"
+  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 "file" of the top non-bugsnag stackframe equals "/usr/src/app/stack_frame_modification/initiators/handled_block.rb"
   And the event "exceptions.0.stacktrace.0.inProject" is null
   And the event "exceptions.0.stacktrace.1.inProject" is true
   And the event "exceptions.0.stacktrace.2.inProject" is true
   And the event "exceptions.0.stacktrace.3.inProject" is true
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |

data/features/plain_features/report_user.feature

@@ -1,118 +1,51 @@
 Feature: Plain report modify user
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
 Scenario Outline: A report can have a user name, email, and id set
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby report_modification/set_user_details.rb"
-  And I wait for 1 second
-  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"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/set_user_details.rb"
+  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.name" equals "leo testman"
   And the event "user.email" equals "test@test.com"
   And the event "user.id" equals "0001"
 
   Examples:
-  | ruby version | initiator               |
-  | 1.9.3        | handled_before_notify   |
-  | 1.9.3        | handled_block           |
-  | 1.9.3        | unhandled_before_notify |
-  | 2.0          | handled_before_notify   |
-  | 2.0          | handled_block           |
-  | 2.0          | unhandled_before_notify |
-  | 2.1          | handled_before_notify   |
-  | 2.1          | handled_block           |
-  | 2.1          | unhandled_before_notify |
-  | 2.2          | handled_before_notify   |
-  | 2.2          | handled_block           |
-  | 2.2          | unhandled_before_notify |
-  | 2.3          | handled_before_notify   |
-  | 2.3          | handled_block           |
-  | 2.3          | unhandled_before_notify |
-  | 2.4          | handled_before_notify   |
-  | 2.4          | handled_block           |
-  | 2.4          | unhandled_before_notify |
-  | 2.5          | handled_before_notify   |
-  | 2.5          | handled_block           |
-  | 2.5          | unhandled_before_notify |
+  | initiator               |
+  | handled_before_notify   |
+  | handled_block           |
+  | unhandled_before_notify |
+  | handled_on_error        |
+  | unhandled_on_error      |
 
 Scenario Outline: A report can have custom info set
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
   And I run the service "plain-ruby" with the command "bundle exec ruby report_modification/set_custom_user_details.rb"
-  And I wait for 1 second
-  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"
+  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.type" equals "amateur"
   And the event "user.location" equals "testville"
   And the event "user.details.a" equals "foo"
   And the event "user.details.b" equals "bar"
 
   Examples:
-  | ruby version | initiator               |
-  | 1.9.3        | handled_before_notify   |
-  | 1.9.3        | handled_block           |
-  | 1.9.3        | unhandled_before_notify |
-  | 2.0          | handled_before_notify   |
-  | 2.0          | handled_block           |
-  | 2.0          | unhandled_before_notify |
-  | 2.1          | handled_before_notify   |
-  | 2.1          | handled_block           |
-  | 2.1          | unhandled_before_notify |
-  | 2.2          | handled_before_notify   |
-  | 2.2          | handled_block           |
-  | 2.2          | unhandled_before_notify |
-  | 2.3          | handled_before_notify   |
-  | 2.3          | handled_block           |
-  | 2.3          | unhandled_before_notify |
-  | 2.4          | handled_before_notify   |
-  | 2.4          | handled_block           |
-  | 2.4          | unhandled_before_notify |
-  | 2.5          | handled_before_notify   |
-  | 2.5          | handled_block           |
-  | 2.5          | unhandled_before_notify |
+  | initiator               |
+  | handled_before_notify   |
+  | handled_block           |
+  | unhandled_before_notify |
+  | handled_on_error        |
+  | unhandled_on_error      |
 
 Scenario Outline: A report can have its user info removed
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby report_modification/remove_user_details.rb"
-  And I wait for 1 second
-  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"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/remove_user_details.rb"
+  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" is null
 
   Examples:
-  | ruby version | initiator               |
-  | 1.9.3        | handled_before_notify   |
-  | 1.9.3        | handled_block           |
-  | 1.9.3        | unhandled_before_notify |
-  | 2.0          | handled_before_notify   |
-  | 2.0          | handled_block           |
-  | 2.0          | unhandled_before_notify |
-  | 2.1          | handled_before_notify   |
-  | 2.1          | handled_block           |
-  | 2.1          | unhandled_before_notify |
-  | 2.2          | handled_before_notify   |
-  | 2.2          | handled_block           |
-  | 2.2          | unhandled_before_notify |
-  | 2.3          | handled_before_notify   |
-  | 2.3          | handled_block           |
-  | 2.3          | unhandled_before_notify |
-  | 2.4          | handled_before_notify   |
-  | 2.4          | handled_block           |
-  | 2.4          | unhandled_before_notify |
-  | 2.5          | handled_before_notify   |
-  | 2.5          | handled_block           |
-  | 2.5          | unhandled_before_notify |
+  | initiator               |
+  | handled_before_notify   |
+  | handled_block           |
+  | unhandled_before_notify |
+  | handled_on_error        |
+  | unhandled_on_error      |