QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

I have read the prd, checked the products lifecycle and the modules available on SLES15SP4, conclusions as below:
For SLES migration path:
From sles12sp3 (TBD), sles12sp4, sles12sp5, sles15sp2, sles15sp3, sles15sp4 to sles15sp5

• So comparing with the current cases in migration groups, the test coverage changes are the to be added sles15sp4 migration path and the to be removed SLES15SP1 migration path (and might need to remove sles12sp3 migration path which is still TBD) PS: on the ha migration confluence page, the migration path of sles15sp1 is listed, need to confirm it with PM, because on prd, it states that migration from SLE15SPx to SLE15SPx+3 is supported, from SLE15SPx to SLE15SPx+4 is NOT supported.
• For the new cases of sles15sp4 -> sles15sp5, python3 module is a new module that available since sle15sp4, need to add it for migration testing.

For SLED migration path:
From sled15sp4

For HPC migration path:
From sle-hpc-15sp4
I'll create migration matrix (add the cases of SLE15SP4) next Monday and send to team.

I created the draft of sle15sp5 migration matrix, and shared it with team via sharepoint for review.
BTW, the work flow of making migration matrix is:

1. reading PRD to confirm the supported migration path
2. create cases in migration matrix
3. send the matrix to team for review
4. then send to PM to review the matrix (because the matrix is based on PRD, while sometimes the PRD might have errors or just a draft at the early phase of a under developing product)
5. modify matrix if any feedback from PM
6. when no problems with the matrix, deploy the cases to openQA