-
Epic
-
Resolution: Unresolved
-
Major
-
2.2.0.GA
-
CRW pre-release testing scalability
-
To Do
-
14% To Do, 0% In Progress, 86% Done
In order to obtain the scalability and speed up the testing it needs to avoid manual interventions during the pre release testing as much as possible.
This epic will cover all issues devoted to 100% of pre release automation.
The list of QE manual efforts:
Not automated notification when new bits have arrived to trigger the pre release testing Jenkins jobs.
Installation of OCP sometimes fails that leads to manual interventions to re-run the job.
CodeReady test cases updating should be automated. After any changes in test files a trigger will start a job that update test cases list on Polarion
Creation of test Runs in Polarion is particalary automated (somebody has to run the script and manualy perform some tuning in Polarion). For now we can improve this by Jenkins job creation that will create all test runs.
Setting the Fail/Pass status on test cases in Polarion must be automated for automated tests
Manual testing of not automated test cases in test plan
Manual verification of fixed bugs. With having velocity QE are not able to verify all bug fixes.
Automation of Release Readiness document (creating/updating of Metrics) to provide the always up-to-date readout for stake holders
OCP interop testing is not automated
There is just dummy test in Quality gate in CVP that should be extended to smoke test suite.
- relates to
-
CRW-1030 Migrate CRW build system to CPaaS
- Closed