bugsnag 6.13.1 → 6.18.0

data/features/plain_features/ignore_classes.feature

@@ -1,11 +0,0 @@
-Feature: Plain ignore classes
-
-Scenario Outline: An errors class is in the ignore_classes array
-  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 no requests
-
-  Examples:
-  | state     |
-  | unhandled |
-  | handled   |

data/features/plain_features/ignore_report.feature

@@ -1,12 +0,0 @@
-Feature: Plain ignore report
-
-Scenario Outline: A reports severity can be modified
-  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 no requests
-
-  Examples:
-  | initiator               |
-  | handled_before_notify   |
-  | unhandled_before_notify |

data/features/plain_features/proxies.feature

@@ -1,25 +0,0 @@
-Feature: proxy configuration options
-
-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"
-  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"
-
-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"
-
-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"

data/features/plain_features/release_stages.feature

@@ -1,20 +0,0 @@
-Feature: Release stage configuration options
-
-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"
-  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 no requests
-
-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"
-  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"

data/features/plain_features/report_api_key.feature

@@ -1,14 +0,0 @@
-Feature: Plain report modify api key
-
-Scenario Outline: A report can have its api_key modified
-  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:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |

data/features/plain_features/report_severity.feature

@@ -1,15 +0,0 @@
-Feature: Plain report modify severity
-
-Scenario Outline: A reports severity can be modified
-  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:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |

data/features/plain_features/report_stack_frames.feature

@@ -1,49 +0,0 @@
-Feature: Plain report modify stack frames
-
-Scenario Outline: Stack frames can be removed
-  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:
-  | initiator               | lineNumber |
-  | handled_before_notify   | 20         |
-  | unhandled_before_notify | 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
-
-Scenario Outline: Stack frames can be marked as in project
-  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
-  And the event "exceptions.0.stacktrace.2.inProject" is true
-  And the event "exceptions.0.stacktrace.3.inProject" is true
-
-  Examples:
-  | initiator               |
-  | handled_before_notify   |
-  | unhandled_before_notify |
-
-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 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

data/features/plain_features/report_user.feature

@@ -1,45 +0,0 @@
-Feature: Plain report modify user
-
-Scenario Outline: A report can have a user name, email, and id set
-  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:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |
-
-Scenario Outline: A report can have custom info set
-  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 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:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |
-
-Scenario Outline: A report can have its user info removed
-  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:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |

data/features/plain_features/unhandled_errors.feature

@@ -1,33 +0,0 @@
-Feature: Plain unhandled errors
-
-Scenario Outline: An unhandled error sends a report
-  Given I run the service "plain-ruby" with the command "bundle exec ruby unhandled/<file>.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 "<error>"
-  And the "file" of stack frame 0 equals "/usr/src/app/unhandled/<file>.rb"
-  And the "lineNumber" of stack frame 0 equals <lineNumber>
-
-  Examples:
-  | file              | error          | lineNumber |
-  | runtime_error     | RuntimeError   | 6          |
-  | load_error        | LoadError      | 6          |
-  | syntax_error      | SyntaxError    | 6          |
-  | local_jump_error  | LocalJumpError | 7          |
-  | name_error        | NameError      | 6          |
-  | no_method_error   | NoMethodError  | 6          |
-  | system_call_error | Errno::ENOENT  | 6          |
-  | custom_error      | CustomError    | 9          |
-
-Scenario Outline: An unhandled error doesn't send a report
-  When I run the service "plain-ruby" with the command "bundle exec ruby unhandled/<file>.rb"
-  And I wait for 1 second
-  Then I should receive no requests
-
-  Examples:
-  | file          |
-  | interrupt     |
-  | system_exit   |

data/features/rails_features/api_key.feature

@@ -1,15 +0,0 @@
-Feature: API key
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Setting api_key in environment variable works
-  Given I start the rails service
-  When I navigate to the route "/api_key/environment" 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"
-
-@rails3 @rails4 @rails5 @rails6
- Scenario Outline: Changing api_key after initializer works
-  Given I start the rails service
-  When I navigate to the route "/api_key/changing?api_key=c35a2a72bd230ac0aa0f52715bbdc6ac" 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"

data/features/rails_features/app_type.feature

@@ -1,24 +0,0 @@
-Feature: App type configuration
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Setting app_type in initializer works
-  Given I set environment variable "BUGSNAG_APP_TYPE" to "custom_app_type"
-  And I start the rails service
-  When I navigate to the route "/app_type/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.request.url" ends with "/app_type/initializer"
-  And the event "app.type" equals "custom_app_type"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Changing app_type after initializer works
-  Given I start the rails service
-  When I navigate to the route "/app_type/after?type=maze_after_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.request.url" ends with "/app_type/after?type=maze_after_initializer"
-  And the event "app.type" equals "maze_after_initializer"

data/features/rails_features/app_version.feature

@@ -1,26 +0,0 @@
-Feature: App version configuration
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: App_version is nil by default
-  Given I start the rails service
-  When I navigate to the route "/app_version/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.version" is null
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Setting app_version in initializer works
-  Given I set environment variable "BUGSNAG_APP_VERSION" to "1.0.0"
-  And I start the rails service
-  When I navigate to the route "/app_version/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 "app.version" equals "1.0.0"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Setting app_version after initializer works
-  Given I start the rails service
-  When I navigate to the route "/app_version/after?version=1.1.0" 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.version" equals "1.1.0"

data/features/rails_features/auto_capture_sessions.feature

@@ -1,34 +0,0 @@
-Feature: Auto capture sessions
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Auto_capture_sessions defaults to true
-  Given I set environment variable "USE_DEFAULT_AUTO_CAPTURE_SESSIONS" to "true"
-  And I start the rails service
-  When I navigate to the route "/session_tracking/initializer" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the session reporting API version "1.0" for the "Ruby Bugsnag Notifier" notifier
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Auto_capture_sessions can be set to false in the initializer
-  Given I set environment variable "BUGSNAG_AUTO_CAPTURE_SESSIONS" to "false"
-  And I start the rails service
-  When I navigate to the route "/session_tracking/initializer" on the rails app
-  And I wait for 3 seconds
-  Then I should receive no requests
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Manual sessions are still sent if Auto_capture_sessions is false
-  Given I set environment variable "BUGSNAG_AUTO_CAPTURE_SESSIONS" to "false"
-  And I start the rails service
-  When I navigate to the route "/session_tracking/manual" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the session reporting API version "1.0" for the "Ruby Bugsnag Notifier" notifier
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: 100 session calls results in 100 sessions
-  Given I set environment variable "BUGSNAG_AUTO_CAPTURE_SESSIONS" to "false"
-  And I start the rails service
-  When I navigate to the route "/session_tracking/multi_sessions" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the session reporting API version "1.0" for the "Ruby Bugsnag Notifier" notifier
-  And the total sessionStarted count equals 100

data/features/rails_features/auto_notify.feature

@@ -1,41 +0,0 @@
-Feature: Auto notify
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Auto_notify set to false in the initializer prevents unhandled error sending
-  Given I set environment variable "BUGSNAG_AUTO_NOTIFY" to "false"
-  And I start the rails service
-  When I navigate to the route "/auto_notify/unhandled" on the rails app
-  And I wait for 3 seconds
-  Then I should receive no requests
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Auto_notify set to false in the initializer still sends handled errors
-  Given I set environment variable "BUGSNAG_AUTO_NOTIFY" to "false"
-  And I start the rails service
-  When I navigate to the route "/auto_notify/handled" 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 false
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/auto_notify/handled"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Auto_notify set to false after the initializer prevents unhandled error sending
-  Given I start the rails service
-  When I navigate to the route "/auto_notify/unhandled_after" on the rails app
-  And I wait for 3 seconds
-  Then I should receive no requests
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Auto_notify set to false after the initializer still sends handled errors
-  Given I start the rails service
-  When I navigate to the route "/auto_notify/handled_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 exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "unhandled" is false
-  And the event "metaData.request.url" ends with "/auto_notify/handled_after"
-  And the event "app.type" equals "rails"

data/features/rails_features/before_notify.feature

@@ -1,44 +0,0 @@
-Feature: Before notify callbacks
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Rails before_notify controller method works on handled errors
-  Given I start the rails service
-  When I navigate to the route "/before_notify/handled" 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 "unhandled" is false
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/before_notify/handled"
-  And the event "metaData.before_notify.source" equals "rails_before_handled"
-  And the event "metaData.controller.name" equals "BeforeNotifyController"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Rails before_notify controller method works on unhandled errors
-  Given I start the rails service
-  When I navigate to the route "/before_notify/unhandled" 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 "NameError"
-  And the exception "message" starts with "undefined local variable or method `generate_unhandled_error' for #<BeforeNotifyController"
-  And the event "unhandled" is true
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/before_notify/unhandled"
-  And the event "metaData.before_notify.source" equals "rails_before_unhandled"
-  And the event "metaData.controller.name" equals "BeforeNotifyController"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Inline block on handled errors is called
-  Given I start the rails service
-  When I navigate to the route "/before_notify/inline" 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 "unhandled" is false
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/before_notify/inline"
-  And the event "metaData.before_notify.source" equals "rails_inline"
-  And the event "metaData.controller.name" equals "BeforeNotifyController"
-

data/features/rails_features/breadcrumbs.feature

@@ -1,43 +0,0 @@
-Feature: Rails automatic breadcrumbs
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Request breadcrumb
-  Given I start the rails service
-  When I navigate to the route "/breadcrumbs/handled" 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 contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/request.json"
-
-@rails3 @rails4
-Scenario: SQL Breadcrumb without bindings
-  Given I set environment variable "SQL_ONLY_BREADCRUMBS" to "true"
-  And I start the rails service
-  When I navigate to the route "/breadcrumbs/sql_breadcrumb" 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 contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/sql_without_bindings.json"
-
-@rails5 @rails6
-Scenario: SQL Breadcrumb with bindings
-  Given I set environment variable "SQL_ONLY_BREADCRUMBS" to "true"
-  And I start the rails service
-  When I navigate to the route "/breadcrumbs/sql_breadcrumb" 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 contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/sql_with_bindings.json"
-
-@rails4 @rails5 @rails6
-Scenario: Active job breadcrumb
-  Given I start the rails service
-  When I navigate to the route "/breadcrumbs/active_job" 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 contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/active_job.json"
-
-@rails4 @rails5 @rails6
-Scenario: Cache read
-  Given I start the rails service
-  When I navigate to the route "/breadcrumbs/cache_read" 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 has a "process" breadcrumb named "Read cache"