Project

General

Profile

Actions

action #155869

closed

coordination #152769: [epic] Reduction of yaml files in YaST installations

Reduce yaml files for crypt_no_lvm

Added by JERiveraMoya 10 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2024-01-04
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See epic and tickets in the epic for best practices.

Some general summary as a hint (after reading previous tickets):
Main goals are to reduce for single test suite to single yaml file comparing the ones created per each architecture before and drive the schedule having different yaml default files per each architecture. The final yaml should be stored in a folder where we have the representation of each test case: schedule/yam/test_cases
In order to do that you have to consider if it is just about yaml or would require some code changes to make things more homogeneous, there are multiple approaches ranging from simple dropping small tested functionality in some specific architecture to some more fancy code strategy.
At the same time we should care of variables, basically moving all of them to job group yaml.
Leave out for now ppc64le, due to most of our test coverage is in PowerVM and it is not working, so verification are not possible atm. Anyway in the future most likely we will have to reduce hugely test coverage for ppc64le, so we should take that into account instead of trying to do much effort in the code due to PowerVM requires special treatment in the console or installation that only make sense to have them in textmode breaking this homogeneity that we are aiming to.

Specific from this test suite:
None, should be straightforward.
Schedules for this test suite exists in schedule/yast/encryption/.

Acceptance criteria

AC1: Reduce yaml files for corresponding test suite over all the architectures
AC2: Clean-up unused files.

Actions #1

Updated by JERiveraMoya 9 months ago

  • Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
Actions #2

Updated by JERiveraMoya 8 months ago

  • Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
Actions #3

Updated by JERiveraMoya 8 months ago

  • Priority changed from Normal to Low
Actions #4

Updated by JERiveraMoya 7 months ago

  • Priority changed from Low to Normal
Actions #5

Updated by pstivanin 7 months ago

  • Status changed from Workable to In Progress
  • Assignee set to pstivanin
Actions #7

Updated by JERiveraMoya 7 months ago

  • Tags changed from qe-yam-may-sprint to qe-yam-jan-sprint
Actions #8

Updated by pstivanin 7 months ago

  • Status changed from In Progress to Resolved
Actions #9

Updated by JERiveraMoya 7 months ago

  • Tags changed from qe-yam-jan-sprint to qe-yam-jun-sprint
Actions

Also available in: Atom PDF