-
Epic
-
Resolution: Won't Do
-
Critical
-
None
-
None
OCP/Telco Definition of Done
<https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde>
Epic Template descriptions and documentation.
<https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit>
ACM-wide Product Requirements (Top-level Epics)
<https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit>
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
Identify strategies to:
- increase robustness of automated console testing
- reduce instances of broken test cases due to UI changes
- anticipate test case issues or identify problems sooner
- reduce the effort required to identify which changes broke a test case and who can help address the issue
- increase cooperation between development and QE on automated test cases
Why is this important?
- Current test cases break frequently
- Broken test cases are not always discovered right away
- Developers do not have insight into what level of coverage is provided by E2E tests
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
