Skip to content

Commit 2665c49

Browse files
authored
Merge pull request #40 from vi-patel/escalation_policy
[INTEROP-7489] Adding Escalation Process for Failing Scenarios
2 parents f64ea30 + f016164 commit 2665c49

File tree

2 files changed

+17
-0
lines changed

2 files changed

+17
-0
lines changed

docs/Policy/Maintenance/Scenario_Maintenance_Policy.md

+16
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@
1313
- [Triggering Cadence](#triggering-cadence)
1414
- [Reporting Tests](#reporting-tests)
1515
- [Skipping Scenarios](#skipping-scenarios)
16+
- [Escalation Policy for Failing Scenarios](#escalation-policy-for-failing-scenarios)
1617

1718
## Overview
1819

@@ -31,6 +32,7 @@ Scenario maintenance tasks include:
3132
6. Triggering Cadence (CSPI-QE)
3233
7. Reporting Tests (CSPI-QE)
3334
8. Skipping Scenarios (CSPI-QE)
35+
9. Escalation Policy (CSPI-QE)
3436

3537
## Scenario Expansions
3638

@@ -221,3 +223,17 @@ With the introduction of a trigger job we now are able to skip scenario's easily
221223
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`.
222224

223225
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.

docs/SUMMARY.md

+1
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@
3232
- [Scenario Documentation Policy](Policy/Documentation/Scenario_Documentation_Policy.md)
3333
- [Step Registry Documentation Policy](Policy/Documentation/Step_Registry_Documentation_Policy.md)
3434
- [Markdown Resources](Policy/Documentation/Markdown_Resources.md)
35+
- [Scenario Maintenance Policy](Policy/Maintenance/Scenario_Maintenance_Policy.md)
3536

3637
## FAQ
3738

0 commit comments

Comments
 (0)