bugsnag 6.15.0 → 6.27.1

data/features/fixtures/resque/.dockerignore

@@ -1 +0,0 @@
-Gemfile.lock

data/features/fixtures/resque/Dockerfile

@@ -1,14 +0,0 @@
-ARG RUBY_TEST_VERSION
-FROM ruby:$RUBY_TEST_VERSION
-
-WORKDIR /bugsnag
-COPY temp-bugsnag-lib ./
-
-WORKDIR /usr/src/app
-COPY app/Gemfile /usr/src/app/
-RUN bundle install
-
-COPY . /usr/src/app
-ENV QUEUE=*
-
-CMD ["bundle", "exec", "rake", "resque:work"]

data/features/fixtures/resque/Gemfile

@@ -1,6 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'bugsnag', path: '/bugsnag'
-gem 'resque'
-gem 'rake'
-gem 'redis'

data/features/fixtures/resque/Rakefile

@@ -1,4 +0,0 @@
-load 'app.rb'
-require 'resque/tasks'
-
-Resque.redis = Redis.new(:url => 'redis://redis:6379')

data/features/fixtures/resque/app.rb

@@ -1,12 +0,0 @@
-require 'bundler'
-Bundler.require
-
-class BugsnagWorker
-  @queue = :compute
-
-  def self.perform(operation, a, b)
-    puts "Work started for #{operation} on #{a} and #{b}"
-    sleep 5
-    puts "#{a} #{operation} #{b} = #{a.send(operation, b)}"
-  end
-end

data/features/fixtures/sidekiq/.dockerignore

@@ -1,2 +0,0 @@
-Gemfile.lock
-payloads/

data/features/fixtures/sidekiq/Dockerfile

@@ -1,17 +0,0 @@
-ARG RUBY_TEST_VERSION
-FROM ruby:$RUBY_TEST_VERSION
-
-WORKDIR /bugsnag
-COPY temp-bugsnag-lib ./
-
-ARG APP_PATH
-
-WORKDIR /app/
-
-COPY app/Gemfile Gemfile
-ARG SIDEKIQ_VERSION
-ENV SIDEKIQ_VERSION $SIDEKIQ_VERSION
-
-RUN bundle install
-
-COPY app/ /app/

data/features/fixtures/sidekiq/app/Gemfile

@@ -1,7 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'bugsnag', path: '/bugsnag'
-gem 'sidekiq', ENV['SIDEKIQ_VERSION']
-gem 'timers', '~> 4.1.1'
-gem 'redis', '~> 3.3.5'
-gem 'rake', '~> 12.3.0'

data/features/fixtures/sidekiq/app/Rakefile.rb

@@ -1,14 +0,0 @@
-namespace :sidekiq_tests do
-  task :handled_error do
-    run_sidekiq_test('./initializers/HandledError.rb')
-  end
-
-  task :unhandled_error do
-    run_sidekiq_test('./initializers/UnhandledError.rb')
-  end
-end
-
-def run_sidekiq_test(command)
-  system("ruby #{command}")
-  system("sidekiq -r ./app.rb")
-end

data/features/fixtures/sidekiq/app/app.rb

@@ -1,35 +0,0 @@
-require 'bundler'
-Bundler.require
-
-Bugsnag.configure do |conf|
-  puts "Configuring `api_key` to #{ENV['BUGSNAG_API_KEY']}"
-  conf.api_key = ENV['BUGSNAG_API_KEY']
-  puts "Configuring `endpoint` to #{ENV['BUGSNAG_ENDPOINT']}"
-  conf.endpoint = ENV['BUGSNAG_ENDPOINT']
-end
-
-Sidekiq.configure_client do |config|
-  config.redis = { :url => 'redis://redis:6379', :size => 1 }
-end
-
-Sidekiq.configure_server do |config|
-  config.redis = { :url => 'redis://redis:6379' }
-end
-
-class HandledError
-  include Sidekiq::Worker
-  sidekiq_options :retry => false
-
-  def perform
-    Bugsnag.notify(RuntimeError.new("Handled"))
-  end
-end
-
-class UnhandledError
-  include Sidekiq::Worker
-  sidekiq_options :retry => false
-
-  def perform
-    raise RuntimeError.new("Unhandled")
-  end
-end

data/features/fixtures/sidekiq/app/initializers/HandledError.rb

@@ -1,3 +0,0 @@
-require './app.rb'
-
-HandledError.perform_async

data/features/fixtures/sidekiq/app/initializers/UnhandledError.rb

@@ -1,3 +0,0 @@
-require './app.rb'
-
-UnhandledError.perform_async

data/features/fixtures/sidekiq/payloads/handled_metadata_ca_false.json

@@ -1,11 +0,0 @@
-{
-    "msg": {
-        "class": "HandledError",
-        "args": [],
-        "retry": false,
-        "queue": "default",
-        "jid": "IGNORE",
-        "enqueued_at": "IGNORE"
-    },
-    "queue": "default"
-}

data/features/fixtures/sidekiq/payloads/handled_metadata_ca_true.json

@@ -1,12 +0,0 @@
-{
-    "msg": {
-        "class": "HandledError",
-        "args": [],
-        "retry": false,
-        "queue": "default",
-        "jid": "IGNORE",
-        "created_at": "IGNORE",
-        "enqueued_at": "IGNORE"
-    },
-    "queue": "default"
-}

data/features/fixtures/sidekiq/payloads/unhandled_metadata_ca_false.json

@@ -1,11 +0,0 @@
-{
-    "msg": {
-        "class": "UnhandledError",
-        "args": [],
-        "retry": false,
-        "queue": "default",
-        "jid": "IGNORE",
-        "enqueued_at": "IGNORE"
-    },
-    "queue": "default"
-}

data/features/fixtures/sidekiq/payloads/unhandled_metadata_ca_true.json

@@ -1,12 +0,0 @@
-{
-    "msg": {
-        "class": "UnhandledError",
-        "args": [],
-        "retry": false,
-        "queue": "default",
-        "jid": "IGNORE",
-        "created_at": "IGNORE",
-        "enqueued_at": "IGNORE"
-    },
-    "queue": "default"
-}

data/features/fixtures/sinatra1/.dockerignore

@@ -1 +0,0 @@
-Gemfile.lock

data/features/fixtures/sinatra1/Dockerfile

@@ -1,13 +0,0 @@
-ARG RUBY_TEST_VERSION
-FROM ruby:$RUBY_TEST_VERSION
-
-WORKDIR /bugsnag
-COPY temp-bugsnag-lib ./
-
-WORKDIR /usr/src/app
-COPY app/Gemfile /usr/src/app/
-RUN bundle install
-
-COPY . /usr/src/app
-
-CMD ["ruby", "app.rb"]

data/features/fixtures/sinatra1/Gemfile

@@ -1,4 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'bugsnag', path: '/bugsnag'
-gem 'sinatra', '~> 1'

data/features/fixtures/sinatra1/app.rb

@@ -1,9 +0,0 @@
-require 'bundler'
-Bundler.require
-
-set bind: '0.0.0.0'
-set port: 3000
-
-get '/' do
-  'Hello world!'
-end

data/features/fixtures/sinatra2/.dockerignore

@@ -1 +0,0 @@
-Gemfile.lock

data/features/fixtures/sinatra2/Dockerfile

@@ -1,13 +0,0 @@
-ARG RUBY_TEST_VERSION
-FROM ruby:$RUBY_TEST_VERSION
-
-WORKDIR /bugsnag
-COPY temp-bugsnag-lib ./
-
-WORKDIR /usr/src/app
-COPY app/Gemfile /usr/src/app/
-RUN bundle install
-
-COPY . /usr/src/app
-
-CMD ["ruby", "app.rb"]

data/features/fixtures/sinatra2/Gemfile

@@ -1,4 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'bugsnag', path: '/bugsnag'
-gem 'sinatra', '~> 2'

data/features/fixtures/sinatra2/app.rb

@@ -1,9 +0,0 @@
-require 'bundler'
-Bundler.require
-
-set bind: '0.0.0.0'
-set port: 3000
-
-get '/' do
-  'Hello world!'
-end

data/features/plain_features/add_tab.feature

@@ -1,55 +0,0 @@
-Feature: Plain add tab to metadata
-
-Scenario Outline: Metadata can be added to a report using add_tab
-  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/add_tab.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 "metaData.additional_metadata.foo" equals "foo"
-  And the event "metaData.additional_metadata.bar.0" equals "b"
-  And the event "metaData.additional_metadata.bar.1" equals "a"
-  And the event "metaData.additional_metadata.bar.2" equals "r"
-
-  Examples:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |
-  | handled_on_error        |
-  | unhandled_on_error      |
-
-Scenario Outline: Metadata can be added to an existing tab using add_tab
-  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/add_tab_existing.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 "metaData.additional_metadata.foo" equals "foo"
-  And the event "metaData.additional_metadata.bar.0" equals "b"
-  And the event "metaData.additional_metadata.bar.1" equals "a"
-  And the event "metaData.additional_metadata.bar.2" equals "r"
-  And the event "metaData.additional_metadata.foobar.first" equals "foo"
-  And the event "metaData.additional_metadata.foobar.then" equals "bar"
-
-  Examples:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |
-  | handled_on_error        |
-  | unhandled_on_error      |
-
-Scenario Outline: Metadata can be overwritten using add_tab
-  Given I set environment variable "CALLBACK_INITIATOR" to "<initiator>"
-  When I run the service "plain-ruby" with the command "bundle exec ruby report_modification/add_tab_override.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 "metaData.additional_metadata.foo" equals "foo"
-  And the event "metaData.additional_metadata.bar" equals "bar"
-
-  Examples:
-  | initiator               |
-  | handled_before_notify   |
-  | handled_block           |
-  | unhandled_before_notify |
-  | handled_on_error        |
-  | unhandled_on_error      |

data/features/plain_features/app_type.feature

@@ -1,8 +0,0 @@
-Feature: App type configuration option
-
-Scenario: The App type configuration option can be set
-  Given I set environment variable "BUGSNAG_APP_TYPE" to "test_app"
-  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/send_handled.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 "app.type" equals "test_app"

data/features/plain_features/app_version.feature

@@ -1,8 +0,0 @@
-Feature: App version configuration option
-
-Scenario: The App version configuration option can be set
-  Given I set environment variable "BUGSNAG_APP_VERSION" to "9.9.8"
-  When I run the service "plain-ruby" with the command "bundle exec ruby configuration/send_handled.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 "app.version" equals "9.9.8"

data/features/plain_features/auto_notify.feature

@@ -1,7 +0,0 @@
-Feature: Auto notify configuration option
-
-Scenario: When Auto-notify is false notifications are not sent
-  Given I set environment variable "BUGSNAG_AUTO_NOTIFY" to "false"
-  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

data/features/plain_features/delivery.feature

@@ -1,20 +0,0 @@
-Feature: delivery_method configuration option
-
-Scenario: When the delivery_method is set to :synchronous
-  When I run the service "plain-ruby" with the command "bundle exec ruby delivery/synchronous.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 "metaData.config" matches the JSON fixture in "features/fixtures/plain/json/delivery_synchronous.json"
-
-Scenario: When the delivery_method is set to :thread_queue
-  When I run the service "plain-ruby" with the command "bundle exec ruby delivery/threadpool.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 "metaData.config" matches the JSON fixture in "features/fixtures/plain/json/delivery_threadpool.json"
-
-Scenario: When the delivery_method is set to :thread_queue in a fork
-  When I run the service "plain-ruby" with the command "bundle exec ruby delivery/fork_threadpool.rb"
-  And I wait to receive 2 requests
-  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 event "metaData.config" matches the JSON fixture in "features/fixtures/plain/json/delivery_fork.json"

data/features/plain_features/exception_data.feature

@@ -1,50 +0,0 @@
-Feature: Plain exception data
-
-Scenario Outline: An error has built in meta-data
-  When I run the service "plain-ruby" with the command "bundle exec ruby exception_data/<state>_meta_data.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 exception "errorClass" equals "CustomError"
-  And the event "metaData.exception.exception_type" equals "FATAL"
-  And the event "metaData.exception.exception_base" equals "RuntimeError"
-
-  Examples:
-  | state     |
-  | unhandled |
-  | handled   |
-
-Scenario Outline: An error has built in context
-  When I run the service "plain-ruby" with the command "bundle exec ruby exception_data/<state>_context.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 exception "errorClass" equals "CustomError"
-  And the event "context" equals "IntegrationTests"
-
-  Examples:
-  | state     |
-  | unhandled |
-  | handled   |
-
-Scenario Outline: An error has built in grouping hash
-  When I run the service "plain-ruby" with the command "bundle exec ruby exception_data/<state>_hash.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 exception "errorClass" equals "CustomError"
-  And the event "groupingHash" equals "ABCDE12345"
-
-  Examples:
-  | state     |
-  | unhandled |
-  | handled   |
-
-Scenario Outline: An error has built in user id
-  When I run the service "plain-ruby" with the command "bundle exec ruby exception_data/<state>_user_id.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 exception "errorClass" equals "CustomError"
-  And the event "user.id" equals "000001"
-
-  Examples:
-  | state     |
-  | unhandled |
-  | handled   |

data/features/plain_features/filters.feature

@@ -1,14 +0,0 @@
-Feature: Plain filtering of metadata
-
-Scenario: Metadata is filtered through the default filters
-  When I run the service "plain-ruby" with the command "bundle exec ruby filters/default_filters.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 "metaData.filter" matches the JSON fixture in "features/fixtures/plain/json/filters_default_metadata_filters.json"
-
-Scenario: Additional filters can be added to the filter list
-  Given I set environment variable "BUGSNAG_META_DATA_FILTERS" to "filter_me"
-  When I run the service "plain-ruby" with the command "bundle exec ruby filters/additional_filters.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 "metaData.filter.filter_me" equals "[FILTERED]"

data/features/plain_features/handled_errors.feature

@@ -1,42 +0,0 @@
-Feature: Plain handled errors
-
-Scenario: A rescued exception sends a report
-  When I run the service "plain-ruby" with the command "bundle exec ruby handled/notify_exception.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 false
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-  And the exception "errorClass" equals "RuntimeError"
-  And the "file" of stack frame 0 equals "/usr/src/app/handled/notify_exception.rb"
-  And the "lineNumber" of stack frame 0 equals 6
-
-Scenario: A notified string sends a report
-  When I run the service "plain-ruby" with the command "bundle exec ruby handled/notify_string.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 false
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-  And the exception "errorClass" equals "RuntimeError"
-  And the "file" of the top non-bugsnag stackframe equals "/usr/src/app/handled/notify_string.rb"
-  And the "lineNumber" of the top non-bugsnag stackframe equals 8
-
-Scenario: A handled error doesn't send a report when the :skip_bugsnag flag is set
-  When I run the service "plain-ruby" with the command "bundle exec ruby handled/ignore_exception.rb"
-  And I wait for 1 second
-  Then I should receive no requests
-
-Scenario: A handled error can attach metadata in a block
-  When I run the service "plain-ruby" with the command "bundle exec ruby handled/block_metadata.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 false
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-  And the exception "errorClass" equals "RuntimeError"
-  And the "file" of stack frame 0 equals "/usr/src/app/handled/block_metadata.rb"
-  And the "lineNumber" of stack frame 0 equals 6
-  And the event "metaData.account.id" equals "1234abcd"
-  And the event "metaData.account.name" equals "Acme Co"
-  And the event "metaData.account.support" is true

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,14 +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 |
-  | handled_on_error        |
-  | unhandled_on_error      |

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,16 +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 |
-  | handled_on_error        |
-  | unhandled_on_error      |

data/features/plain_features/report_severity.feature

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

data/features/plain_features/report_stack_frames.feature

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