action #42854: [functional][y][epic] Introduce relevant installation validation test modules
[sle][functional][y] Introduce only relevant tests modules for USBinstall test suite
We already execute same set of test suites on the same setup, except the fact that USB used for installation. So USBinstall test suite performs a lot of actions and creates review overhead not bringing much value.
We need to identify relevant set of test modules, which can be affected by having repo on, e.g. zypper tests, yast_i, updates
- Set of test modules is defined based on the business value of scenario and confirmed by stackholders
- Only relevant test modules are scheduled in the scenario.
INSTALLATION_VALIDATION=... can be used here. We can ask yast team (#yast irc channel on freenode) and RMs.
#9 Updated by okurz over 1 year ago
- Due date changed from 2018-12-04 to 2018-12-18
- Status changed from Resolved to Workable
- Priority changed from Normal to Urgent
As described in #44708#note-6 reopening to handle the direct regression which dimstar first mentioned in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6324#issuecomment-444058428
#10 Updated by JERiveraMoya over 1 year ago
I don't think it is a regression, it is more a false positive. The PR just made it more explicit showing a problem that was hidden: We were enabling the first repo which was not usb and was already enabled (because there are not usb repos in ths scenario).
There is no need for this test on that testsuite and possible bad use of the variable USBBOOT.
#11 Updated by riafarov over 1 year ago
I also believe that it depends on the point of view. Objectively this change has exposed problem we always had. In the end I don't care how we solve this, I was fine with the new ticket. I also want to emphasize that JERiveraMoya has identified this problem and created ticket, that's really well done and shows that we cared about potential issues. So thanks for that! As for ticket, please handle it any way you comfortable with, either here, or we can use the one you've created and anyone from the team can pick it up.