-
Notifications
You must be signed in to change notification settings - Fork 21
/
Copy pathhandled-view.feature
31 lines (29 loc) · 1.53 KB
/
handled-view.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Feature: Handled exceptions in views
Scenario: Handled exceptions are delivered from views
Given I start the symfony fixture
When I navigate to the route "/handled/view/exception"
Then I wait to receive an error
And the error is valid for the error reporting API version "4.0" for the "Bugsnag Symfony" notifier
And the exception "errorClass" equals "LogicException"
And the exception "message" equals "Handled exception"
And the event "metaData.request.httpMethod" equals "GET"
And the event "metaData.request.url" ends with "/handled/view/exception"
And the event "app.type" equals "HTTP"
And the event "context" equals "GET /handled/view/exception"
And the event "severity" equals "warning"
And the event "unhandled" is false
And the event "severityReason.type" equals "handledException"
Scenario: Handled errors are delivered from views
Given I start the symfony fixture
When I navigate to the route "/handled/view/error"
Then I wait to receive an error
And the error is valid for the error reporting API version "4.0" for the "Bugsnag Symfony" notifier
And the exception "errorClass" equals "A handled error"
And the exception "message" equals "handled"
And the event "metaData.request.httpMethod" equals "GET"
And the event "metaData.request.url" ends with "/handled/view/error"
And the event "app.type" equals "HTTP"
And the event "context" equals "GET /handled/view/error"
And the event "severity" equals "warning"
And the event "unhandled" is false
And the event "severityReason.type" equals "handledError"