bugsnag 6.12.0 → 6.14.0

data/features/plain_features/filters.feature

@@ -1,48 +1,14 @@
 Feature: Plain filtering of metadata
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Metadata is filtered through the default filters
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby filters/default_filters.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"
+Scenario: Metadata is filtered through the default filters
+  When I run the service "plain-ruby" with the command "bundle exec ruby filters/default_filters.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 "metaData.filter" matches the JSON fixture in "features/fixtures/plain/json/filters_default_metadata_filters.json"
 
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-Scenario Outline: Additional filters can be added to the filter list
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "BUGSNAG_META_DATA_FILTERS" to "filter_me"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby filters/additional_filters.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"
+Scenario: Additional filters can be added to the filter list
+  Given I set environment variable "BUGSNAG_META_DATA_FILTERS" to "filter_me"
+  When I run the service "plain-ruby" with the command "bundle exec ruby filters/additional_filters.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 "metaData.filter.filter_me" equals "[FILTERED]"
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |

data/features/plain_features/handled_errors.feature

@@ -1,18 +1,9 @@
 Feature: Plain handled errors
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: A rescued exception sends a report
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby handled/notify_exception.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"
+Scenario: A rescued exception sends a report
+  When I run the service "plain-ruby" with the command "bundle exec ruby handled/notify_exception.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 false
   And the event "severity" equals "warning"
   And the event "severityReason.type" equals "handledException"
@@ -20,25 +11,10 @@ Scenario Outline: A rescued exception sends a report
   And the "file" of stack frame 0 equals "/usr/src/app/handled/notify_exception.rb"
   And the "lineNumber" of stack frame 0 equals 6
 
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-Scenario Outline: A notified string sends a report
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby handled/notify_string.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"
+Scenario: A notified string sends a report
+  When I run the service "plain-ruby" with the command "bundle exec ruby handled/notify_string.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 false
   And the event "severity" equals "warning"
   And the event "severityReason.type" equals "handledException"
@@ -46,43 +22,15 @@ Scenario Outline: A notified string sends a report
   And the "file" of the top non-bugsnag stackframe equals "/usr/src/app/handled/notify_string.rb"
   And the "lineNumber" of the top non-bugsnag stackframe equals 8
 
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-
-Scenario Outline: A handled error doesn't send a report when the :skip_bugsnag flag is set
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby handled/ignore_exception.rb"
+Scenario: A handled error doesn't send a report when the :skip_bugsnag flag is set
+  When I run the service "plain-ruby" with the command "bundle exec ruby handled/ignore_exception.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: A handled error can attach metadata in a block
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby handled/block_metadata.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"
+Scenario: A handled error can attach metadata in a block
+  When I run the service "plain-ruby" with the command "bundle exec ruby handled/block_metadata.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 false
   And the event "severity" equals "warning"
   And the event "severityReason.type" equals "handledException"
@@ -91,14 +39,4 @@ Scenario Outline: A handled error can attach metadata in a block
   And the "lineNumber" of stack frame 0 equals 6
   And the event "metaData.account.id" equals "1234abcd"
   And the event "metaData.account.name" equals "Acme Co"
-  And the event "metaData.account.support" is true
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
+  And the event "metaData.account.support" is true

data/features/plain_features/ignore_classes.feature

@@ -1,29 +1,11 @@
 Feature: Plain ignore classes
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
 Scenario Outline: An errors class is in the ignore_classes array
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby ignore_classes/<state>.rb"
+  When I run the service "plain-ruby" with the command "bundle exec ruby ignore_classes/<state>.rb"
   And I wait for 1 second
-  Then I should receive 0 requests
+  Then I should receive no requests
 
   Examples:
-  | ruby version | state     |
-  | 1.9.3        | unhandled |
-  | 1.9.3        | handled   |
-  | 2.0          | unhandled |
-  | 2.0          | handled   |
-  | 2.1          | unhandled |
-  | 2.1          | handled   |
-  | 2.2          | unhandled |
-  | 2.2          | handled   |
-  | 2.3          | unhandled |
-  | 2.3          | handled   |
-  | 2.4          | unhandled |
-  | 2.4          | handled   |
-  | 2.5          | unhandled |
-  | 2.5          | handled   |
+  | state     |
+  | unhandled |
+  | handled   |

data/features/plain_features/ignore_report.feature

@@ -1,30 +1,12 @@
 Feature: Plain ignore report
 
-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/ignore_report.rb"
+  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
+  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/ignore_report.rb"
   And I wait for 1 second
-  Then I should receive 0 requests
+  Then I should receive no requests
 
   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 |
+  | initiator               |
+  | handled_before_notify   |
+  | unhandled_before_notify |

data/features/plain_features/proxies.feature

@@ -1,68 +1,25 @@
 Feature: proxy configuration options
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Proxy settings are provided as configuration options
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "BUGSNAG_PROXY_HOST" to the current IP
-  And I set environment variable "BUGSNAG_PROXY_PORT" to the mock API port
+Scenario: Proxy settings are provided as configuration options
+  When I set environment variable "BUGSNAG_PROXY_HOST" to "maze-runner"
+  And I set environment variable "BUGSNAG_PROXY_PORT" to "9339"
   And I set environment variable "BUGSNAG_PROXY_USER" to "tester"
   And I set environment variable "BUGSNAG_PROXY_PASSWORD" to "testpass"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby configuration/proxy.rb"
-  And I wait for 1 second
-  Then I should receive a request
+  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/proxy.rb"
+  Then I wait to receive a request
   And the "proxy-authorization" header equals "Basic dGVzdGVyOnRlc3RwYXNz"
   And the event "metaData.proxy.user" equals "tester"
 
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-Scenario Outline: Proxy settings are provided as the HTTP_PROXY environment variable
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "http_proxy" to the proxy settings with credentials "http://tester:testpass"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby configuration/proxy.rb"
-  And I wait for 1 second
-  Then I should receive a request
+Scenario: Proxy settings are provided as the HTTP_PROXY environment variable
+  Given I set environment variable "http_proxy" to "http://tester:testpass@maze-runner:9339"
+  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/proxy.rb"
+  Then I wait to receive a request
   And the "proxy-authorization" header equals "Basic dGVzdGVyOnRlc3RwYXNz"
   And the event "metaData.proxy.user" equals "tester"
 
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-Scenario Outline: Proxy settings are provided as the HTTPS_PROXY environment variable
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "https_proxy" to the proxy settings with credentials "https://tester:testpass"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby configuration/proxy.rb"
-  And I wait for 1 second
-  Then I should receive a request
+Scenario: Proxy settings are provided as the HTTPS_PROXY environment variable
+  Given I set environment variable "https_proxy" to "http://tester:testpass@maze-runner:9339"
+  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/proxy.rb"
+  Then I wait to receive a request
   And the "proxy-authorization" header equals "Basic dGVzdGVyOnRlc3RwYXNz"
   And the event "metaData.proxy.user" equals "tester"
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |

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,14 @@
 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 |

data/features/plain_features/report_severity.feature

@@ -1,42 +1,15 @@
 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 |