-
Notifications
You must be signed in to change notification settings - Fork 174
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update to allow hackathon to be demonstrated
- Loading branch information
Showing
3 changed files
with
72 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
source "https://rubygems.org" | ||
|
||
gem 'bugsnag-maze-runner', git: 'https://github.com/bugsnag/maze-runner', tag: 'v7.10.1' | ||
gem 'bugsnag-maze-runner', git: 'https://github.com/bugsnag/maze-runner', branch: 'integration/hackathon-2024' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
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 an error | ||
Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" 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 last event is available via the data access api | ||
And the pipeline event payload field "metaData.additional_metadata.foo" equals "foo" | ||
And the pipeline event payload field "metaData.additional_metadata.bar.0" equals "b" | ||
And the pipeline event payload field "metaData.additional_metadata.bar.1" equals "a" | ||
And the pipeline event payload field "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 an error | ||
Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" 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" | ||
And the last event is available via the data access api | ||
And the pipeline event payload field "metaData.additional_metadata.foo" equals "foo" | ||
And the pipeline event payload field "metaData.additional_metadata.bar.0" equals "b" | ||
And the pipeline event payload field "metaData.additional_metadata.bar.1" equals "a" | ||
And the pipeline event payload field "metaData.additional_metadata.bar.2" equals "r" | ||
And the pipeline event payload field "metaData.additional_metadata.foobar.first" equals "foo" | ||
And the pipeline event payload field "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 an error | ||
Then the error is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier" notifier | ||
And the event "metaData.additional_metadata.foo" equals "foo" | ||
And the event "metaData.additional_metadata.bar" equals "bar" | ||
And the last event is available via the data access api | ||
And the pipeline event payload field "metaData.additional_metadata.foo" equals "foo" | ||
And the pipeline event payload field "metaData.additional_metadata.bar" equals "bar" | ||
|
||
Examples: | ||
| initiator | | ||
| handled_before_notify | | ||
| handled_block | | ||
| unhandled_before_notify | | ||
| handled_on_error | | ||
| unhandled_on_error | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters