Sha256: 701da15d255de29c8356af738a2819847df6d0497e883a5fd52422ad9fc0e7dd

Contents?: true

Size: 1.13 KB

Versions: 4

Compression:

Stored size: 1.13 KB

Contents

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"

Version data entries

4 entries across 4 versions & 1 rubygems

Version Path
bugsnag-6.15.0 features/plain_features/release_stages.feature
bugsnag-6.14.0 features/plain_features/release_stages.feature
bugsnag-6.13.1 features/plain_features/release_stages.feature
bugsnag-6.13.0 features/plain_features/release_stages.feature