action #155866
open
coordination #152769: [epic] Reduction of yaml files in YaST installations
Reduce yaml files for create_hdd_transactional_server
Added by JERiveraMoya about 1 year ago.
Updated about 2 months ago.
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/transactional_server
.
Acceptance criteria¶
AC1: Reduce yaml files for corresponding test suite over all the architectures
AC2: Clean-up unused files.
- Copied from action #155863: Reduce yaml files for btrfs+warnings added
- Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
- Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
- Priority changed from Normal to Low
- Priority changed from Low to Normal
- Tags changed from qe-yam-may-sprint to qe-yam-jan-sprint
- Tags changed from qe-yam-jan-sprint to qe-yam-jun-sprint
- Tags changed from qe-yam-jun-sprint to qe-yam-jul-sprint
- Tags changed from qe-yam-jul-sprint, qe-yam-aug-sprint to qe-yam-aug-sprint
- Status changed from Workable to In Progress
- Assignee set to jfernandez
feel free to put in workable some of your ticket for yaml reduction if you are focused on high prio, so we give opportunity to someone else.
- Tags changed from qe-yam-aug-sprint to qe-yam-sep-sprint
- Status changed from In Progress to Workable
- Assignee deleted (
jfernandez)
- Status changed from Workable to In Progress
- Assignee set to zoecao
The [validate_default_target] error on s390x reported in [bsc#1229647] is caused by VNC testing on s390x, so it is closed as invalid by developer. And I skipped the default target checking in tests, [VRs]
Still need to think about how to add one more test module of "shutsown/svirt_upload_assets" for s390x only, I tried to add "conditional_schedule", but it doesn't work, some errors: https://openqa.suse.de/tests/15389474
- Tags deleted (
qe-yam-sep-sprint)
- Status changed from In Progress to New
- Assignee deleted (
zoecao)
- Copied from deleted (action #155863: Reduce yaml files for btrfs+warnings)
- Tags set to qe-yam-oct-sprint
- Status changed from New to Workable
- Tags changed from qe-yam-oct-sprint to qe-yam-nov-sprint
- Status changed from Workable to New
- Status changed from New to Workable
- Tags deleted (
qe-yam-nov-sprint)
- Status changed from Workable to New
- Tags set to qe-yam-jan-sprint-fy25
- Status changed from New to Workable
- Tags changed from qe-yam-jan-sprint-fy25 to qe-yam-dec-sprint-fy25
- Status changed from Workable to New
- Tags deleted (
qe-yam-dec-sprint-fy25)
Also available in: Atom
PDF