bugsnag 6.12.1 → 6.15.0

data/features/plain_features/unhandled_errors.feature

@@ -1,18 +1,9 @@
 Feature: Plain unhandled errors
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I configure the bugsnag endpoint
-
 Scenario Outline: An unhandled error sends a report
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby unhandled/<file>.rb"
-  And I wait for 1 second
-  Then I should receive a request
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request used payload v4 headers
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
+  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"
@@ -21,84 +12,22 @@ Scenario Outline: An unhandled error sends a report
   And the "lineNumber" of stack frame 0 equals <lineNumber>
 
   Examples:
-  | ruby version | file              | error          | lineNumber |
-  | 1.9.3        | runtime_error     | RuntimeError   | 6          |
-  | 1.9.3        | load_error        | LoadError      | 6          |
-  | 1.9.3        | syntax_error      | SyntaxError    | 6          |
-  | 1.9.3        | local_jump_error  | LocalJumpError | 7          |
-  | 1.9.3        | name_error        | NameError      | 6          |
-  | 1.9.3        | no_method_error   | NoMethodError  | 6          |
-  | 1.9.3        | system_call_error | Errno::ENOENT  | 6          |
-  | 1.9.3        | custom_error      | CustomError    | 9          |
-  | 2.0          | runtime_error     | RuntimeError   | 6          |
-  | 2.0          | load_error        | LoadError      | 6          |
-  | 2.0          | syntax_error      | SyntaxError    | 6          |
-  | 2.0          | local_jump_error  | LocalJumpError | 7          |
-  | 2.0          | name_error        | NameError      | 6          |
-  | 2.0          | no_method_error   | NoMethodError  | 6          |
-  | 2.0          | system_call_error | Errno::ENOENT  | 6          |
-  | 2.0          | custom_error      | CustomError    | 9          |
-  | 2.1          | runtime_error     | RuntimeError   | 6          |
-  | 2.1          | load_error        | LoadError      | 6          |
-  | 2.1          | syntax_error      | SyntaxError    | 6          |
-  | 2.1          | local_jump_error  | LocalJumpError | 7          |
-  | 2.1          | name_error        | NameError      | 6          |
-  | 2.1          | no_method_error   | NoMethodError  | 6          |
-  | 2.1          | system_call_error | Errno::ENOENT  | 6          |
-  | 2.1          | custom_error      | CustomError    | 9          |
-  | 2.2          | runtime_error     | RuntimeError   | 6          |
-  | 2.2          | load_error        | LoadError      | 6          |
-  | 2.2          | syntax_error      | SyntaxError    | 6          |
-  | 2.2          | local_jump_error  | LocalJumpError | 7          |
-  | 2.2          | name_error        | NameError      | 6          |
-  | 2.2          | no_method_error   | NoMethodError  | 6          |
-  | 2.2          | system_call_error | Errno::ENOENT  | 6          |
-  | 2.2          | custom_error      | CustomError    | 9          |
-  | 2.3          | runtime_error     | RuntimeError   | 6          |
-  | 2.3          | load_error        | LoadError      | 6          |
-  | 2.3          | syntax_error      | SyntaxError    | 6          |
-  | 2.3          | local_jump_error  | LocalJumpError | 7          |
-  | 2.3          | name_error        | NameError      | 6          |
-  | 2.3          | no_method_error   | NoMethodError  | 6          |
-  | 2.3          | system_call_error | Errno::ENOENT  | 6          |
-  | 2.3          | custom_error      | CustomError    | 9          |
-  | 2.4          | runtime_error     | RuntimeError   | 6          |
-  | 2.4          | load_error        | LoadError      | 6          |
-  | 2.4          | syntax_error      | SyntaxError    | 6          |
-  | 2.4          | local_jump_error  | LocalJumpError | 7          |
-  | 2.4          | name_error        | NameError      | 6          |
-  | 2.4          | no_method_error   | NoMethodError  | 6          |
-  | 2.4          | system_call_error | Errno::ENOENT  | 6          |
-  | 2.4          | custom_error      | CustomError    | 9          |
-  | 2.5          | runtime_error     | RuntimeError   | 6          |
-  | 2.5          | load_error        | LoadError      | 6          |
-  | 2.5          | syntax_error      | SyntaxError    | 6          |
-  | 2.5          | local_jump_error  | LocalJumpError | 7          |
-  | 2.5          | name_error        | NameError      | 6          |
-  | 2.5          | no_method_error   | NoMethodError  | 6          |
-  | 2.5          | system_call_error | Errno::ENOENT  | 6          |
-  | 2.5          | custom_error      | CustomError    | 9          |
+  | 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
-  And I set environment variable "RUBY_VERSION" to "<ruby version>"
-  And I have built the service "plain-ruby"
-  And I run the service "plain-ruby" with the command "bundle exec ruby unhandled/<file>.rb"
+  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 0 requests
+  Then I should receive no requests
 
   Examples:
-  | ruby version | file          |
-  | 1.9.3        | interrupt     |
-  | 1.9.3        | system_exit   |
-  | 2.0          | interrupt     |
-  | 2.0          | system_exit   |
-  | 2.1          | interrupt     |
-  | 2.1          | system_exit   |
-  | 2.2          | interrupt     |
-  | 2.2          | system_exit   |
-  | 2.3          | interrupt     |
-  | 2.3          | system_exit   |
-  | 2.4          | interrupt     |
-  | 2.4          | system_exit   |
-  | 2.5          | interrupt     |
-  | 2.5          | system_exit   |
+  | file          |
+  | interrupt     |
+  | system_exit   |

data/features/rails_features/api_key.feature

@@ -1,61 +1,15 @@
 Feature: API key
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Setting api_key in environment variable works
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_API_KEY" to "b35a2a72bd230ac0aa0f52715bbdc6ab"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/api_key/environment" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "b35a2a72bd230ac0aa0f52715bbdc6ab"
-  And the payload field "events" is an array with 1 element
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
+@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 set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/api_key/changing?api_key=c35a2a72bd230ac0aa0f52715bbdc6ac" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "c35a2a72bd230ac0aa0f52715bbdc6ac"
-  And the payload field "events" is an array with 1 element
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
+  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,69 +1,24 @@
 Feature: App type configuration
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Setting app_type in initializer works
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_APP_TYPE" to "custom_app_type"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/app_type/initializer" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@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"
 
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Changing app_type after initializer works
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/app_type/after?type=maze_after_initializer" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@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"
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |

data/features/rails_features/app_version.feature

@@ -1,87 +1,26 @@
 Feature: App version configuration
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: App_version is nil by default
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/app_version/default" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the payload field "events" is an array with 1 element
+@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
 
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Setting app_version in initializer works
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_APP_VERSION" to "1.0.0"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/app_version/initializer" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@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"
 
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Setting app_version after initializer works
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/app_version/after?version=1.1.0" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the error reporting API
-  And the request contained the api key "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the payload field "events" is an array with 1 element
+@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"
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |

data/features/rails_features/auto_capture_sessions.feature

@@ -1,115 +1,34 @@
 Feature: Auto capture sessions
 
-Background:
-  Given I set environment variable "BUGSNAG_API_KEY" to "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And I set environment variable "APP_PATH" to "/usr/src"
-  And I configure the bugsnag endpoint
-
-Scenario Outline: Auto_capture_sessions defaults to true
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "USE_DEFAULT_AUTO_CAPTURE_SESSIONS" to "true"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/session_tracking/initializer" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the session tracking API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the "Bugsnag-API-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the sessionCount "startedAt" is a timestamp
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Auto_capture_sessions can be set to false in the initializer
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_AUTO_CAPTURE_SESSIONS" to "false"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/session_tracking/initializer" on port "6128<rails_version>"
-  Then I should receive 0 requests
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: Manual sessions are still sent if Auto_capture_sessions is false
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_AUTO_CAPTURE_SESSIONS" to "false"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/session_tracking/manual" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the session tracking API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the "Bugsnag-API-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the sessionCount "startedAt" is a timestamp
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |
-
-Scenario Outline: 100 session calls results in 100 sessions
-  Given I set environment variable "RUBY_VERSION" to "<ruby_version>"
-  And I set environment variable "BUGSNAG_AUTO_CAPTURE_SESSIONS" to "false"
-  And I start the service "rails<rails_version>"
-  And I wait for the app to respond on port "6128<rails_version>"
-  When I navigate to the route "/session_tracking/multi_sessions" on port "6128<rails_version>"
-  Then I should receive a request
-  And the request is a valid for the session tracking API
-  And the request used the "Ruby Bugsnag Notifier" notifier
-  And the "Bugsnag-API-Key" header equals "a35a2a72bd230ac0aa0f52715bbdc6aa"
-  And the sessionCount "startedAt" is a timestamp
+@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
-
-  Examples:
-    | ruby_version | rails_version |
-    | 2.0          | 3             |
-    | 2.1          | 3             |
-    | 2.2          | 3             |
-    | 2.2          | 4             |
-    | 2.2          | 5             |
-    | 2.3          | 3             |
-    | 2.3          | 4             |
-    | 2.3          | 5             |
-    | 2.4          | 3             |
-    | 2.4          | 5             |
-    | 2.5          | 3             |
-    | 2.5          | 5             |
-    | 2.5          | 6             |