From c2ac24f2ed88c6924c100f6daff55bd0de038a39 Mon Sep 17 00:00:00 2001 From: Alex Moinet Date: Mon, 9 Dec 2024 17:15:23 +0000 Subject: [PATCH] Enable rails8 docker container to run --- features/fixtures/docker-compose.yml | 44 +++++++++++++++++++ features/rails_features/active_job.feature | 4 +- features/rails_features/active_record.feature | 2 +- features/rails_features/api_key.feature | 4 +- features/rails_features/app_type.feature | 8 ++-- features/rails_features/app_version.feature | 6 +-- .../auto_capture_sessions.feature | 8 ++-- features/rails_features/auto_notify.feature | 8 ++-- features/rails_features/before_notify.feature | 6 +-- features/rails_features/breadcrumbs.feature | 8 ++-- features/rails_features/feature_flags.feature | 6 +-- features/rails_features/handled.feature | 6 +-- .../rails_features/ignore_classes.feature | 4 +- .../rails_features/meta_data_filters.feature | 2 +- features/rails_features/on_error.feature | 4 +- features/rails_features/project_root.feature | 6 +-- features/rails_features/release_stage.feature | 6 +-- features/rails_features/request.feature | 4 +- features/rails_features/send_code.feature | 4 +- .../rails_features/send_environment.feature | 2 +- features/rails_features/unhandled.feature | 2 +- features/rails_features/user_info.feature | 2 +- 22 files changed, 95 insertions(+), 51 deletions(-) diff --git a/features/fixtures/docker-compose.yml b/features/fixtures/docker-compose.yml index d54d9dd6..d6c7dc58 100644 --- a/features/fixtures/docker-compose.yml +++ b/features/fixtures/docker-compose.yml @@ -300,6 +300,50 @@ services: - target: 3000 published: 7257 + rails8: + build: + context: rails8 + args: + - RUBY_TEST_VERSION + depends_on: + - mongo + environment: + - BUGSNAG_API_KEY + - http_proxy + - RAILS_ENV + - BUGSNAG_APP_TYPE + - BUGSNAG_APP_VERSION + - BUGSNAG_AUTO_CAPTURE_SESSIONS + - BUGSNAG_AUTO_NOTIFY + - BUGSNAG_ENDPOINT + - BUGSNAG_IGNORE_CLASS + - BUGSNAG_IGNORE_MESSAGE + - BUGSNAG_META_DATA_FILTERS + - BUGSNAG_NOTIFY_RELEASE_STAGE + - BUGSNAG_PROJECT_ROOT + - BUGSNAG_PROXY_HOST + - BUGSNAG_PROXY_PASSWORD + - BUGSNAG_PROXY_PORT + - BUGSNAG_PROXY_USER + - BUGSNAG_RELEASE_STAGE + - BUGSNAG_SEND_CODE + - BUGSNAG_SEND_ENVIRONMENT + - BUGSNAG_SESSION_ENDPOINT + - BUGSNAG_TIMEOUT + - CALLBACK_INITIATOR + - SQL_ONLY_BREADCRUMBS + - ADD_ON_ERROR + - USE_DEFAULT_AUTO_CAPTURE_SESSIONS + - ADD_REQUEST_ON_ERROR + restart: "no" + networks: + default: + aliases: + - rails8 + ports: + - target: 3000 + published: 7258 + rails_integrations: build: context: rails_integrations diff --git a/features/rails_features/active_job.feature b/features/rails_features/active_job.feature index 49669fe5..34547574 100644 --- a/features/rails_features/active_job.feature +++ b/features/rails_features/active_job.feature @@ -1,6 +1,6 @@ Feature: Active Job -@rails4 @rails5 @rails6 @rails7 +@rails4 @rails5 @rails6 @rails7 @rails8 Scenario: A handled error will be delivered Given I start the rails service When I navigate to the route "/active_job/handled" on the rails app @@ -26,7 +26,7 @@ Scenario: A handled error will be delivered And in Rails versions ">=" 6 the event "metaData.active_job.timezone" equals "UTC" And in Rails versions ">=" 6 the event "metaData.active_job.enqueued_at" is a timestamp -@rails4 @rails5 @rails6 @rails7 +@rails4 @rails5 @rails6 @rails7 @rails8 Scenario: An unhandled error will be delivered Given I start the rails service When I navigate to the route "/active_job/unhandled" on the rails app diff --git a/features/rails_features/active_record.feature b/features/rails_features/active_record.feature index bed21bd4..fc611169 100644 --- a/features/rails_features/active_record.feature +++ b/features/rails_features/active_record.feature @@ -1,6 +1,6 @@ Feature: Active Record -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: An unhandled error in a transaction callback will be delivered Given I start the rails service When I navigate to the route "/unhandled/error_in_active_record_callback" on the rails app diff --git a/features/rails_features/api_key.feature b/features/rails_features/api_key.feature index 5cf629fd..e7f7fa94 100644 --- a/features/rails_features/api_key.feature +++ b/features/rails_features/api_key.feature @@ -1,13 +1,13 @@ Feature: API key -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 an error Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/app_type.feature b/features/rails_features/app_type.feature index d08822c4..31ea665a 100644 --- a/features/rails_features/app_type.feature +++ b/features/rails_features/app_type.feature @@ -1,6 +1,6 @@ Feature: App type configuration -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -12,7 +12,7 @@ Scenario: Setting app_type in initializer works And the event "metaData.request.url" ends with "/app_type/initializer" And the event "app.type" equals "custom_app_type" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -23,7 +23,7 @@ Scenario: Changing app_type after initializer works And the event "metaData.request.url" ends with "/app_type/after?type=maze_after_initializer" And the event "app.type" equals "maze_after_initializer" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Should default to "rails" for handled errors Given I start the rails service When I navigate to the route "/app_type/handled" on the rails app @@ -32,7 +32,7 @@ Scenario: Should default to "rails" for handled errors And the event "metaData.request.url" ends with "/app_type/handled" And the event "app.type" equals "rails" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Should default to "rails" for unhandled errors Given I start the rails service When I navigate to the route "/app_type/unhandled" on the rails app diff --git a/features/rails_features/app_version.feature b/features/rails_features/app_version.feature index ac1c612b..0d4e5eb3 100644 --- a/features/rails_features/app_version.feature +++ b/features/rails_features/app_version.feature @@ -1,6 +1,6 @@ Feature: App version configuration -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -8,7 +8,7 @@ Scenario: App_version is nil by default Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event "app.version" is null -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -17,7 +17,7 @@ Scenario: Setting app_version in initializer works Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event "app.version" equals "1.0.0" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/auto_capture_sessions.feature b/features/rails_features/auto_capture_sessions.feature index 01a4d239..0122da8a 100644 --- a/features/rails_features/auto_capture_sessions.feature +++ b/features/rails_features/auto_capture_sessions.feature @@ -1,6 +1,6 @@ Feature: Auto capture sessions -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -8,14 +8,14 @@ Scenario: Auto_capture_sessions defaults to true And I wait to receive a session Then the session is valid for the session reporting API version "1.0" for the "Ruby Bugsnag Notifier" notifier -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 Then I should receive no requests -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -23,7 +23,7 @@ Scenario: Manual sessions are still sent if Auto_capture_sessions is false And I wait to receive a session Then the session is valid for the session reporting API version "1.0" for the "Ruby Bugsnag Notifier" notifier -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/auto_notify.feature b/features/rails_features/auto_notify.feature index 8ff9ca2b..7fcfe809 100644 --- a/features/rails_features/auto_notify.feature +++ b/features/rails_features/auto_notify.feature @@ -1,13 +1,13 @@ Feature: Auto notify -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 Then I should receive no requests -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -20,13 +20,13 @@ Scenario: Auto_notify set to false in the initializer still sends handled errors And the event "app.type" equals "rails" And the event "metaData.request.url" ends with "/auto_notify/handled" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 Then I should receive no requests -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/before_notify.feature b/features/rails_features/before_notify.feature index f337e6d9..d971bb1b 100644 --- a/features/rails_features/before_notify.feature +++ b/features/rails_features/before_notify.feature @@ -1,6 +1,6 @@ Feature: Before notify callbacks -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -14,7 +14,7 @@ Scenario: Rails before_notify controller method works on handled errors And the event "metaData.before_notify.source" equals "rails_before_handled" And the event "metaData.controller.name" equals "BeforeNotifyController" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -28,7 +28,7 @@ Scenario: Rails before_notify controller method works on unhandled errors And the event "metaData.before_notify.source" equals "rails_before_unhandled" And the event "metaData.controller.name" equals "BeforeNotifyController" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/breadcrumbs.feature b/features/rails_features/breadcrumbs.feature index e5d53e35..df95dbca 100644 --- a/features/rails_features/breadcrumbs.feature +++ b/features/rails_features/breadcrumbs.feature @@ -1,6 +1,6 @@ Feature: Rails automatic breadcrumbs -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Request breadcrumb Given I start the rails service When I navigate to the route "/breadcrumbs/handled?password=secret&abc=xyz" on the rails app @@ -17,7 +17,7 @@ Scenario: SQL Breadcrumb without bindings Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/sql_without_bindings.json" -@rails5 @rails6 @rails7 +@rails5 @rails6 @rails7 @rails8 Scenario: SQL Breadcrumb with bindings Given I set environment variable "SQL_ONLY_BREADCRUMBS" to "true" And I start the rails service @@ -26,7 +26,7 @@ Scenario: SQL Breadcrumb with bindings Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/sql_with_bindings.json" -@rails4 @rails5 @rails6 @rails7 +@rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Active job breadcrumb Given I start the rails service When I navigate to the route "/breadcrumbs/active_job" on the rails app @@ -34,7 +34,7 @@ Scenario: Active job breadcrumb Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/active_job.json" -@rails4 @rails5 @rails6 @rails7 +@rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Cache read Given I start the rails service When I navigate to the route "/breadcrumbs/cache_read" on the rails app diff --git a/features/rails_features/feature_flags.feature b/features/rails_features/feature_flags.feature index 3e18c266..e4ec432b 100644 --- a/features/rails_features/feature_flags.feature +++ b/features/rails_features/feature_flags.feature @@ -1,6 +1,6 @@ Feature: feature flags -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: adding feature flags for an unhandled error Given I start the rails service When I navigate to the route "/features/unhandled?flags[a]=1&flags[b]&flags[c]=3&flags[d]=4" on the rails app @@ -32,7 +32,7 @@ Scenario: adding feature flags for an unhandled error | y | | | z | 7 | -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: adding feature flags for a handled error Given I start the rails service When I navigate to the route "/features/handled?flags[ab]=12&flags[cd]=34" on the rails app @@ -62,7 +62,7 @@ Scenario: adding feature flags for a handled error | f | i | | g | | -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: clearing all feature flags doesn't affect subsequent requests Given I start the rails service When I navigate to the route "/features/unhandled?flags[a]=1&flags[b]&flags[c]=3&flags[d]=4&clear_all_flags" on the rails app diff --git a/features/rails_features/handled.feature b/features/rails_features/handled.feature index ea9b22a2..d9dd4998 100644 --- a/features/rails_features/handled.feature +++ b/features/rails_features/handled.feature @@ -1,6 +1,6 @@ Feature: Rails handled errors -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Unhandled RuntimeError Given I start the rails service When I navigate to the route "/handled/unthrown" on the rails app @@ -14,7 +14,7 @@ Scenario: Unhandled RuntimeError And the event "severity" equals "warning" And the event "severityReason.type" equals "handledException" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Thrown handled NameError Given I start the rails service When I navigate to the route "/handled/thrown" on the rails app @@ -28,7 +28,7 @@ Scenario: Thrown handled NameError And the event "severity" equals "warning" And the event "severityReason.type" equals "handledException" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Manual string notify Given I start the rails service When I navigate to the route "/handled/string_notify" on the rails app diff --git a/features/rails_features/ignore_classes.feature b/features/rails_features/ignore_classes.feature index e5f01568..ae134a21 100644 --- a/features/rails_features/ignore_classes.feature +++ b/features/rails_features/ignore_classes.feature @@ -1,13 +1,13 @@ Feature: Ignore classes -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/meta_data_filters.feature b/features/rails_features/meta_data_filters.feature index 5fca2327..49a76b76 100644 --- a/features/rails_features/meta_data_filters.feature +++ b/features/rails_features/meta_data_filters.feature @@ -1,6 +1,6 @@ Feature: Metadata filters -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/on_error.feature b/features/rails_features/on_error.feature index 94e6e81a..65f776df 100644 --- a/features/rails_features/on_error.feature +++ b/features/rails_features/on_error.feature @@ -1,6 +1,6 @@ Feature: On error callbacks -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Rails on_error works on handled errors Given I set environment variable "ADD_ON_ERROR" to "true" And I start the rails service @@ -14,7 +14,7 @@ Scenario: Rails on_error works on handled errors 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 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Rails on_error works on unhandled errors Given I set environment variable "ADD_ON_ERROR" to "true" And I start the rails service diff --git a/features/rails_features/project_root.feature b/features/rails_features/project_root.feature index b25f6cfa..c3fbed0a 100644 --- a/features/rails_features/project_root.feature +++ b/features/rails_features/project_root.feature @@ -1,6 +1,6 @@ Feature: Project root configuration -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -11,7 +11,7 @@ Scenario: Project_root should default to Rails.root 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 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -23,7 +23,7 @@ Scenario: Project_root can be set in an initializer 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 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/release_stage.feature b/features/rails_features/release_stage.feature index 8accedfb..27b534a1 100644 --- a/features/rails_features/release_stage.feature +++ b/features/rails_features/release_stage.feature @@ -1,6 +1,6 @@ Feature: Release stage -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Release_stage should default to RAILS_ENV Given I set environment variable "RAILS_ENV" to "rails_env" And I start the rails service @@ -9,7 +9,7 @@ Scenario: Release_stage should default to RAILS_ENV Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event "app.releaseStage" equals "rails_env" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -18,7 +18,7 @@ Scenario: Release_stage can be set in an initializer Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event "app.releaseStage" equals "maze_release_stage_env" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/request.feature b/features/rails_features/request.feature index e7f23c49..d2998af0 100644 --- a/features/rails_features/request.feature +++ b/features/rails_features/request.feature @@ -1,6 +1,6 @@ Feature: Request data -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Request data is collected automatically Given I start the rails service When I navigate to the route "/unhandled/error?a=123&b=456" on the rails app @@ -24,7 +24,7 @@ Scenario: Request data is collected automatically And the event "metaData.request.requestId" is not null And the event "metaData.request.url" ends with "/unhandled/error?a=123&b=456" -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Request data can be modified in callbacks Given I set environment variable "ADD_REQUEST_ON_ERROR" to "true" And I start the rails service diff --git a/features/rails_features/send_code.feature b/features/rails_features/send_code.feature index 7f97ed8a..a07f8c01 100644 --- a/features/rails_features/send_code.feature +++ b/features/rails_features/send_code.feature @@ -1,6 +1,6 @@ Feature: Send code -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 @@ -9,7 +9,7 @@ Scenario: Send_code can be updated in an initializer Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier And the event "exceptions.0.stacktrace.0.code" is null -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/send_environment.feature b/features/rails_features/send_environment.feature index 9bfefa7f..e2f8f8d9 100644 --- a/features/rails_features/send_environment.feature +++ b/features/rails_features/send_environment.feature @@ -1,6 +1,6 @@ Feature: Send environment -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 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 diff --git a/features/rails_features/unhandled.feature b/features/rails_features/unhandled.feature index f226cd94..b6254f21 100644 --- a/features/rails_features/unhandled.feature +++ b/features/rails_features/unhandled.feature @@ -1,6 +1,6 @@ Feature: Unhandled exceptions support -@rails3 @rails4 @rails5 @rails6 @rails7 +@rails3 @rails4 @rails5 @rails6 @rails7 @rails8 Scenario: Unhandled RuntimeError Given I start the rails service When I navigate to the route "/unhandled/error" on the rails app diff --git a/features/rails_features/user_info.feature b/features/rails_features/user_info.feature index 3207b694..dea6dd92 100644 --- a/features/rails_features/user_info.feature +++ b/features/rails_features/user_info.feature @@ -34,7 +34,7 @@ Scenario Outline: Devise user information is sent | handled | | unhandled | -@rails5 @rails6 @rails7 +@rails5 @rails6 @rails7 @rails8 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