You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -221,3 +223,17 @@ With the introduction of a trigger job we now are able to skip scenario's easily
221
223
This file holds a list of all job names for our program and a value `active` which will be either true or false. When we need to skip a scenario for whatever reason we just need to edit the file in vault to turn `active: true` to `active: false`.
222
224
223
225
This action is restricted to only a handful of people in the CSPI-QE org.
226
+
227
+
## Escalation Policy for Failing Scenarios
228
+
229
+
All the scenarios should be passing unless there is a known bug associated with the product or platform.
230
+
231
+
An escalation policy is followed for scenarios that fail w/o an associated product/platform issues that are left running multiple weeks without an update.
232
+
This means the product team was tagged on ticket for a failed scenario and took no action to resolve the issue for multiple cycles.
233
+
234
+
The escalation policy will be followed as described here:
235
+
236
+
* Interop QE will notify the Interop manager to escalate the blocked scenario
237
+
* From here, the product QE manager will be notified
238
+
* The isssue will be reflected on the OpenShift program calls until action is taken to resolve the issue.
239
+
* The final step would be to disable the scenario until action is taken by the PQE team to get the scenario passing successfully or log an bug associated with the failure.
0 commit comments