@@ -10,14 +10,14 @@ Feature: On-Call
1010 And an instance of "On-Call" API
1111
1212 @generated @skip @team:DataDog/bugle
13- Scenario : Create on call escalation policy returns "Bad Request" response
13+ Scenario : Create on- call escalation policy returns "Bad Request" response
1414 Given new "CreateOnCallEscalationPolicy" request
1515 And body with value {"data" : {"attributes" : {"description" : "Escalation Policy 1 description" , "name" : "Escalation Policy 1" , "resolve_page_on_policy_end" : true, "retries" : 2, "steps" : [{"assignment" : "default" , "escalate_after_seconds" : 3600, "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-aba2-0000-0000-000000000000" , "type" : "schedules" }, {"id" : "00000000-aba3-0000-0000-000000000000" , "type" : "teams" }]}, {"assignment" : "round-robin" , "escalate_after_seconds" : 3600, "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-abb1-0000-0000-000000000000" , "type" : "users" }]}]}, "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "policies" }}
1616 When the request is sent
1717 Then the response status is 400 Bad Request
1818
1919 @team:DataDog/bugle
20- Scenario : Create on call escalation policy returns "Created" response
20+ Scenario : Create on- call escalation policy returns "Created" response
2121 Given new "CreateOnCallEscalationPolicy" request
2222 And there is a valid "schedule" in the system
2323 And there is a valid "dd_team" in the system
@@ -43,7 +43,7 @@ Feature: On-Call
4343 Then the response status is 201 Created
4444
4545 @team:DataDog/bugle
46- Scenario : Delete on call escalation policy returns "No Content" response
46+ Scenario : Delete on- call escalation policy returns "No Content" response
4747 Given new "DeleteOnCallEscalationPolicy" request
4848 And there is a valid "user" in the system
4949 And there is a valid "dd_team" in the system
@@ -54,7 +54,7 @@ Feature: On-Call
5454 Then the response status is 204 No Content
5555
5656 @generated @skip @team:DataDog/bugle
57- Scenario : Delete on call escalation policy returns "Not Found" response
57+ Scenario : Delete on- call escalation policy returns "Not Found" response
5858 Given new "DeleteOnCallEscalationPolicy" request
5959 And request contains "policy_id" parameter from "REPLACE.ME"
6060 When the request is sent
@@ -76,21 +76,21 @@ Feature: On-Call
7676 Then the response status is 404 Not Found
7777
7878 @generated @skip @team:DataDog/bugle
79- Scenario : Get on call escalation policy returns "Bad Request" response
79+ Scenario : Get on- call escalation policy returns "Bad Request" response
8080 Given new "GetOnCallEscalationPolicy" request
8181 And request contains "policy_id" parameter from "REPLACE.ME"
8282 When the request is sent
8383 Then the response status is 400 Bad Request
8484
8585 @generated @skip @team:DataDog/bugle
86- Scenario : Get on call escalation policy returns "Not Found" response
86+ Scenario : Get on- call escalation policy returns "Not Found" response
8787 Given new "GetOnCallEscalationPolicy" request
8888 And request contains "policy_id" parameter from "REPLACE.ME"
8989 When the request is sent
9090 Then the response status is 404 Not Found
9191
9292 @team:DataDog/bugle
93- Scenario : Get on call escalation policy returns "OK" response
93+ Scenario : Get on- call escalation policy returns "OK" response
9494 Given new "GetOnCallEscalationPolicy" request
9595 And there is a valid "user" in the system
9696 And there is a valid "dd_team" in the system
@@ -116,23 +116,23 @@ Feature: On-Call
116116 Then the response status is 200 OK
117117
118118 @generated @skip @team:DataDog/bugle
119- Scenario : Update on call escalation policy returns "Bad Request" response
119+ Scenario : Update on- call escalation policy returns "Bad Request" response
120120 Given new "UpdateOnCallEscalationPolicy" request
121121 And request contains "policy_id" parameter from "REPLACE.ME"
122122 And body with value {"data" : {"attributes" : {"description" : "Escalation Policy 1 description" , "name" : "Escalation Policy 1" , "resolve_page_on_policy_end" : false, "retries" : 2, "steps" : [{"assignment" : "default" , "escalate_after_seconds" : 3600, "id" : "00000000-aba1-0000-0000-000000000000" , "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-aba2-0000-0000-000000000000" , "type" : "schedules" }]}]}, "id" : "a3000000-0000-0000-0000-000000000000" , "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "policies" }}
123123 When the request is sent
124124 Then the response status is 400 Bad Request
125125
126126 @generated @skip @team:DataDog/bugle
127- Scenario : Update on call escalation policy returns "Not Found" response
127+ Scenario : Update on- call escalation policy returns "Not Found" response
128128 Given new "UpdateOnCallEscalationPolicy" request
129129 And request contains "policy_id" parameter from "REPLACE.ME"
130130 And body with value {"data" : {"attributes" : {"description" : "Escalation Policy 1 description" , "name" : "Escalation Policy 1" , "resolve_page_on_policy_end" : false, "retries" : 2, "steps" : [{"assignment" : "default" , "escalate_after_seconds" : 3600, "id" : "00000000-aba1-0000-0000-000000000000" , "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-aba2-0000-0000-000000000000" , "type" : "schedules" }]}]}, "id" : "a3000000-0000-0000-0000-000000000000" , "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "policies" }}
131131 When the request is sent
132132 Then the response status is 404 Not Found
133133
134134 @team:DataDog/bugle
135- Scenario : Update on call escalation policy returns "OK" response
135+ Scenario : Update on- call escalation policy returns "OK" response
136136 Given new "UpdateOnCallEscalationPolicy" request
137137 And there is a valid "user" in the system
138138 And there is a valid "dd_team" in the system
0 commit comments