bugsnag 6.7.3 → 6.8.0

data/features/plain_features/ignore_report.feature

@@ -0,0 +1,32 @@
+Feature: Plain ignore report
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  Given I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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

@@ -0,0 +1,70 @@
+Feature: proxy configuration options
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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 "MAZE_PROXY_HOST" to the current IP
+  And I set environment variable "MAZE_PROXY_PORT" to the mock API port
+  And I set environment variable "MAZE_PROXY_USER" to "tester"
+  And I set environment variable "MAZE_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          |

data/features/plain_features/release_stages.feature

@@ -0,0 +1,53 @@
+Feature: Release stage configuration options
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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 "MAZE_NOTIFY_RELEASE_STAGE" to "stage_one"
+  And I set environment variable "MAZE_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"
+  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: Doesn't notify in the wrong release stage
+  Given I set environment variable "RUBY_VERSION" to "<ruby version>"
+  And I set environment variable "MAZE_NOTIFY_RELEASE_STAGE" to "stage_one"
+  And I set environment variable "MAZE_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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And the event "unhandled" is true
+  And the event "severity" is "error"
+  And the event "severityReason.type" is "unhandledException"
+  And the exception "errorClass" equals "RuntimeError"
+  And the "file" of stack frame 0 equals "/usr/src/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

@@ -0,0 +1,42 @@
+Feature: Plain report modify api key
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  Given I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "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 |

data/features/plain_features/report_severity.feature

@@ -0,0 +1,44 @@
+Feature: Plain report modify severity
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  Given I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And the event "severity" is "info"
+  And the event "severityReason.type" is "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 |

data/features/plain_features/report_stack_frames.feature

@@ -0,0 +1,84 @@
+Feature: Plain report modify stack frames
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  Given I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And the "file" of stack frame 0 equals "/usr/src/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        | handled_block           | 19         |
+  | 1.9.3        | unhandled_before_notify | 21         |
+  | 2.0          | handled_before_notify   | 20         |
+  | 2.0          | handled_block           | 19         |
+  | 2.0          | unhandled_before_notify | 21         |
+  | 2.1          | handled_before_notify   | 20         |
+  | 2.1          | handled_block           | 19         |
+  | 2.1          | unhandled_before_notify | 21         |
+  | 2.2          | handled_before_notify   | 20         |
+  | 2.2          | handled_block           | 19         |
+  | 2.2          | unhandled_before_notify | 21         |
+  | 2.3          | handled_before_notify   | 20         |
+  | 2.3          | handled_block           | 19         |
+  | 2.3          | unhandled_before_notify | 21         |
+  | 2.4          | handled_before_notify   | 20         |
+  | 2.4          | handled_block           | 19         |
+  | 2.4          | unhandled_before_notify | 21         |
+  | 2.5          | handled_before_notify   | 20         |
+  | 2.5          | handled_block           | 19         |
+  | 2.5          | unhandled_before_notify | 21         |
+
+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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And the "file" of stack frame 0 equals "/usr/src/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
+  And the event "exceptions.0.stacktrace.2.inProject" is true
+  And the event "exceptions.0.stacktrace.3.inProject" is true
+
+  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 |

data/features/plain_features/report_user.feature

@@ -0,0 +1,120 @@
+Feature: Plain report modify user
+
+Background:
+  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  Given I set environment variable "MAZE_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And I set environment variable "APP_PATH" to "/usr/src"
+  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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And the event "user.name" is "leo testman"
+  And the event "user.email" is "test@test.com"
+  And the event "user.id" is "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 |
+
+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"
+  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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  And the event "user.type" is "amateur"
+  And the event "user.location" is "testville"
+  And the event "user.details.a" is "foo"
+  And the event "user.details.b" is "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 |
+
+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 notifier
+  And the request used payload v4 headers
+  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  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 |