bugsnag 6.12.2 → 6.16.0

data/features/plain_features/auto_notify.feature

@@ -1,23 +0,0 @@
-Feature: Auto notify configuration option
-
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: When Auto-notify is false notifications are not sent
-  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I set environment variable "BUGSNAG_AUTO_NOTIFY" to "false"
-  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 0 requests
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |

data/features/plain_features/delivery.feature

@@ -1,68 +0,0 @@
-Feature: delivery_method configuration option
-
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: When the delivery_method is set to :synchronous
-  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 delivery/synchronous.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 contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the exception "errorClass" equals "RuntimeError"
-  And the event "metaData.config" matches the JSON fixture in "features/fixtures/plain/json/delivery_synchronous.json"
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-Scenario Outline: When the delivery_method is set to :thread_queue
-  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 delivery/threadpool.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 contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the exception "errorClass" equals "RuntimeError"
-  And the event "metaData.config" matches the JSON fixture in "features/fixtures/plain/json/delivery_threadpool.json"
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |
-
-Scenario Outline: When the delivery_method is set to :thread_queue in a fork
-  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 delivery/fork_threadpool.rb"
-  And I wait for 1 second
-  Then I should receive 2 requests
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the exception "errorClass" equals "RuntimeError"
-  And the event "metaData.config" matches the JSON fixture in "features/fixtures/plain/json/delivery_fork.json"
-
-  Examples:
-  | ruby version |
-  | 1.9.3        |
-  | 2.0          |
-  | 2.1          |
-  | 2.2          |
-  | 2.3          |
-  | 2.4          |
-  | 2.5          |

data/features/plain_features/exception_data.feature

@@ -1,120 +0,0 @@
-Feature: Plain exception data
-
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: An error has built in meta-data
-  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 exception_data/<state>_meta_data.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 contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the exception "errorClass" equals "CustomError"
-  And the event "metaData.exception.exception_type" equals "FATAL"
-  And the event "metaData.exception.exception_base" equals "RuntimeError"
-
-  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   |
-
-Scenario Outline: An error has built in context
-  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 exception_data/<state>_context.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 the exception "errorClass" equals "CustomError"
-  And the event "context" equals "IntegrationTests"
-
-  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   |
-
-Scenario Outline: An error has built in grouping hash
-  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 exception_data/<state>_hash.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 contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the exception "errorClass" equals "CustomError"
-  And the event "groupingHash" equals "ABCDE12345"
-
-  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   |
-
-Scenario Outline: An error has built in user id
-  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 exception_data/<state>_user_id.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 the exception "errorClass" equals "CustomError"
-  And the event "user.id" equals "000001"
-
-  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   |

data/features/plain_features/filters.feature

@@ -1,48 +0,0 @@
-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"
-  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"
-  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,104 +0,0 @@
-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"
-  And the event "unhandled" is false
-  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/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"
-  And the event "unhandled" is false
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-  And the exception "errorClass" equals "RuntimeError"
-  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"
-  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          |
-
-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"
-  And the event "unhandled" is false
-  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/handled/block_metadata.rb"
-  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          |

data/features/plain_features/ignore_classes.feature

@@ -1,29 +0,0 @@
-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"
-  And I wait for 1 second
-  Then I should receive 0 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   |

data/features/plain_features/ignore_report.feature

@@ -1,30 +0,0 @@
-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"
-  And I wait for 1 second
-  Then I should receive 0 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 |

data/features/plain_features/proxies.feature

@@ -1,68 +0,0 @@
-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
-  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
-  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
-  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
-  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          |