Sha256: 22d6087afaaf713eec396cbd97deaf36032979bafc39c82ceeb0df5ae454a7fb
Contents?: true
Size: 1.32 KB
Versions: 4
Compression:
Stored size: 1.32 KB
Contents
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"
Version data entries
4 entries across 4 versions & 1 rubygems