bugsnag 6.15.0 → 6.27.1

data/features/plain_features/report_user.feature

@@ -1,51 +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 |
-  | handled_on_error        |
-  | unhandled_on_error      |
-
-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 |
-  | handled_on_error        |
-  | unhandled_on_error      |
-
-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 |
-  | handled_on_error        |
-  | unhandled_on_error      |

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"

data/features/rails_features/handled.feature

@@ -1,42 +0,0 @@
-Feature: Rails handled errors
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Unhandled RuntimeError
-  Given I start the rails service
-  When I navigate to the route "/handled/unthrown" 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 unthrown error"
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/handled/unthrown"
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Thrown handled NameError
-  Given I start the rails service
-  When I navigate to the route "/handled/thrown" 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 #<HandledController"
-  And the event "unhandled" is false
-  And the event "metaData.request.url" ends with "/handled/thrown"
-  And the event "app.type" equals "rails"
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Manual string notify
-  Given I start the rails service
-  When I navigate to the route "/handled/string_notify" 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 "/handled/string_notify"
-  And the event "app.type" equals "rails"
-

data/features/rails_features/ignore_classes.feature

@@ -1,14 +0,0 @@
-Feature: Ignore classes
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Ignore_classes can be set to a different value in initializer
-  Given I set environment variable "BUGSNAG_IGNORE_CLASS" to "IgnoredError"
-  And I start the rails service
-  When I navigate to the route "/ignore_classes/initializer" on the rails app
-  Then I should receive no requests
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Ignore_classes can be set to a different value after initializer
-  Given I start the rails service
-  When I navigate to the route "/ignore_classes/after?ignore=IgnoredError" on the rails app
-  Then I should receive no requests

data/features/rails_features/meta_data_filters.feature

@@ -1,16 +0,0 @@
-Feature: Metadata filters
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Meta_data_filters should include Rails.configuration.filter_parameters
-  Given I start the rails service
-  When I navigate to the route "/metadata_filters/filter?filtered_parameter=foo&other_parameter=bar" 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 "/metadata_filters/filter?filtered_parameter=[FILTERED]&other_parameter=bar"
-  And the event "metaData.my_specific_filter" equals "[FILTERED]"
-  And the event "metaData.request.params.filtered_parameter" equals "[FILTERED]"
-  And the event "metaData.request.params.other_parameter" equals "bar"

data/features/rails_features/mongo_breadcrumbs.feature

@@ -1,26 +0,0 @@
-Feature: Mongo automatic breadcrumbs
-
-@rails4 @rails5 @rails6
-Scenario: Successful breadcrumbs
-  Given I start the rails service
-  When I navigate to the route "/mongo/success_crash" 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/mongo_success.json"
-
-@rails4 @rails5 @rails6
-Scenario: Breadcrumb with filter parameters
-  Given I start the rails service
-  When I navigate to the route "/mongo/get_crash" 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/mongo_filtered_request.json"
-  And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/mongo_filtered_result.json"
-
-@rails4 @rails5 @rails6
-Scenario: Failure breadcrumbs
-  Given I start the rails service
-  When I navigate to the route "/mongo/failure_crash" 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/mongo_failed.json"

data/features/rails_features/on_error.feature

@@ -1,29 +0,0 @@
-Feature: On error callbacks
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Rails on_error works on handled errors
-  Given I set environment variable "ADD_ON_ERROR" to "true"
-  And I start the rails service
-  When I navigate to the route "/handled/unthrown" 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 unthrown error"
-  And the event "unhandled" is false
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/handled/unthrown"
-  And the event "metaData.on_error.source" equals "on_error handled"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Rails on_error works on unhandled errors
-  Given I set environment variable "ADD_ON_ERROR" to "true"
-  And I start the rails service
-  When I navigate to the route "/unhandled/error" 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 #<UnhandledController"
-  And the event "unhandled" is true
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/unhandled/error"
-  And the event "metaData.on_error.source" equals "on_error unhandled"

data/features/rails_features/project_root.feature

@@ -1,35 +0,0 @@
-Feature: Project root configuration
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Project_root should default to Rails.root
-  Given I start the rails service
-  When I navigate to the route "/project_root/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 exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "metaData.request.url" ends with "/project_root/default"
-  And the "file" of the top non-bugsnag stackframe equals "app/controllers/project_root_controller.rb"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Project_root can be set in an initializer
-  Given I set environment variable "BUGSNAG_PROJECT_ROOT" to "/foo/bar"
-  And I start the rails service
-  When I navigate to the route "/project_root/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 "/project_root/initializer"
-  And the "file" of the top non-bugsnag stackframe equals "/usr/src/app/controllers/project_root_controller.rb"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Project_root can be set after an initializer
-  Given I start the rails service
-  When I navigate to the route "/project_root/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 "metaData.request.url" ends with "/project_root/after"
-  And the "file" of the top non-bugsnag stackframe equals "/usr/src/app/controllers/project_root_controller.rb"

data/features/rails_features/release_stage.feature

@@ -1,27 +0,0 @@
-Feature: Release stage
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Release_stage should default to RAILS_ENV
-  Given I set environment variable "RAILS_ENV" to "rails_env"
-  And I start the rails service
-  When I navigate to the route "/release_stage/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.releaseStage" equals "rails_env"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Release_stage can be set in an initializer
-  Given I set environment variable "BUGSNAG_RELEASE_STAGE" to "maze_release_stage_env"
-  And I start the rails service
-  When I navigate to the route "/release_stage/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.releaseStage" equals "maze_release_stage_env"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Release_stage can be set after an initializer
-  Given I start the rails service
-  When I navigate to the route "/release_stage/after?stage=set_after_env" 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.releaseStage" equals "set_after_env"

data/features/rails_features/send_code.feature

@@ -1,18 +0,0 @@
-Feature: Send code
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Send_code can be updated in an initializer
-  Given I set environment variable "BUGSNAG_SEND_CODE" to "false"
-  And I start the rails service
-  When I navigate to the route "/send_code/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 "exceptions.0.stacktrace.0.code" is null
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Send_code can be updated after an initializer
-  Given I start the rails service
-  When I navigate to the route "/send_code/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 event "exceptions.0.stacktrace.0.code" is null

data/features/rails_features/send_environment.feature

@@ -1,13 +0,0 @@
-Feature: Send environment
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Send_environment should send environment in handled errors when true
-  Given I set environment variable "BUGSNAG_SEND_ENVIRONMENT" to "true"
-  And I start the rails service
-  When I navigate to the route "/send_environment/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.environment.REQUEST_METHOD" equals "GET"
-  And the event "app.type" equals "rails"

data/features/rails_features/unhandled.feature

@@ -1,16 +0,0 @@
-Feature: Unhandled exceptions support
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Unhandled RuntimeError
-  Given I start the rails service
-  When I navigate to the route "/unhandled/error" 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 true
-  And the exception "errorClass" equals "NameError"
-  And the exception "message" starts with "undefined local variable or method `generate_unhandled_error' for #<UnhandledController"
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/unhandled/error"
-  And the event "severity" equals "error"
-  And the event "severityReason.type" equals "unhandledExceptionMiddleware"
-  And the event "severityReason.attributes.framework" equals "Rack"

data/features/rails_features/user_info.feature

@@ -1,52 +0,0 @@
-Feature: Capture user information
-
-@rails3
-Scenario Outline: Warden user information is sent
-  Given I start the rails service
-  When I navigate to the route "/warden/create" on the rails app
-  And I navigate to the route "/warden/<route>?email=testtest@test.test" 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 "user.email" equals "testtest@test.test"
-  And the event "user.name" equals "Warden User"
-  And the event "user.first_name" equals "Warden"
-  And the event "user.last_name" equals "User"
-
-  Examples:
-    | route     |
-    | handled   |
-    | unhandled |
-
-@rails4
-Scenario Outline: Devise user information is sent
-  Given I start the rails service
-  When I navigate to the route "/devise/create" on the rails app
-  And I navigate to the route "/devise/<route>" 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 "user.email" equals "test+test@test.test"
-  And the event "user.name" equals "Devise User"
-  And the event "user.first_name" equals "Devise"
-  And the event "user.last_name" equals "User"
-
-  Examples:
-    | route     |
-    | handled   |
-    | unhandled |
-
-@rails5 @rails6
-Scenario Outline: Clearance user information is sent
-  Given I start the rails service
-  When I navigate to the route "/clearance/create" on the rails app
-  And I navigate to the route "/clearance/<route>" 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 "user.email" equals "testtest@test.test"
-  And the event "user.name" equals "Clearance User"
-  And the event "user.first_name" equals "Clearance"
-  And the event "user.last_name" equals "User"
-
-  Examples:
-    | route     |
-    | handled   |
-    | unhandled |