action #163280
closedcoordination #152769: [epic] Reduction of yaml files in YaST installations
Reduce yaml files for skip_registration
0%
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.
Specific from this test suite:
Schedules for this test suite exists in schedule/yast/skip_registration.
Acceptance criteria¶
AC1: Reduce yaml files for corresponding test suite over all the architectures.
AC2: Clean-up unused files and other improvements (read epic to refresh about those enhancements).
Updated by jfernandez 7 months ago
- Status changed from Workable to In Progress
- Assignee set to jfernandez
Updated by rainerkoenig 7 months ago
- Tags changed from qe-yam-jul-sprint, qe-yam-aug-sprint to qe-yam-aug-sprint
Updated by JERiveraMoya 7 months ago
- Status changed from In Progress to Resolved
Updated by leli 6 months ago
- Status changed from Resolved to Workable
As https://suse.slack.com/archives/C02CLB2LB7Z/p1724211033236679, I'd reopen this ticket to fix the regression issue.
Updated by openqa_review 4 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: skip_registration
https://openqa.suse.de/tests/15723960#step/zypper_lifecycle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 88 days if nothing changes in this ticket.
Updated by JERiveraMoya 4 months ago
- Tags changed from qe-yam-aug-sprint to qe-yam-oct-sprint
- Status changed from Workable to In Progress
@jfernandez could you please take a look?
Updated by jfernandez 4 months ago
Revert PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20457 (Solves x86_64/aarch64 errors) not solve ppc64le zypper_lifecycle error
MR: https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/349
Updated by JERiveraMoya 4 months ago
- Tags changed from qe-yam-oct-sprint to qe-yam-nov-sprint
Updated by openqa_review 4 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: skip_registration
https://openqa.suse.de/tests/15824911#step/zypper_lifecycle/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by JERiveraMoya 4 months ago
Merged, let's restart to see that all is ok, if not, we send additional fixes.
Updated by JERiveraMoya 4 months ago
- Status changed from In Progress to Resolved