-
Task
-
Resolution: Unresolved
-
Blocker
-
None
-
None
-
None
-
13
-
False
-
-
False
-
subs-swatch-lightning
-
-
-
Swatch Lightning Sprint 2
Determine if it's safe to do a prod release based on this https://reportportal-smqe.apps.dno.ocp-hub.prod.psi.redhat.com/ui/#subscription_watch/launches/all/347065?item0Params=filter.eq.hasStats%3Dtrue%26filter.eq.hasChildren%3Dfalse%26filter.in.type%3DSTEP%26filter.in.status%3DFAILED.
I've prepopulated this card with subtasks based on those failures, filtered down to just the ones that are pertinent to what subs-swatch-lightning works on (thanks rhn-sqe-tmcknigh for helping with this!). I assigned priority of each subtask based on the "importance" level that was assigned to the test in report portal as a starting place.
Acceptance Criteria
- Investigate each of the failing tests
- For each one, determine if the failure is a symptom of a flaky test, or something that needs to be addressed before we can release to production.
- Use the "Convert to Task" on the subtasks in Jira at the conclusion of the investigation of that failing test. Update the priority accordingly. "Blocker" priority should be used to indicate "we should NOT release to production if this test is failing".
- Blocker test failures should be considered for injecting into the sprint
- If one of the subtasks that are pre-populated with "Blocker" priority isn't actually a blocker for release, please bump the priority down.
- Cards for failing tests that were deemed to not block release should be put in the Backlog.
- clones
-
SWATCH-3974 Evaluate post-stage test failures to prepare for prod release
-
- In Progress
-
- relates to
-
SWATCH-4109 Adding the ephemeral Only Marker to tests to help stabilize them
-
- In Progress
-
-
SWATCH-4108 Add a retry in 504 and 500 error the method 'add_sku'
-
- New
-