action #108227
Updated by JERiveraMoya about 2 years ago
#### Motivation We perform registration of an unregistered system in test suite select_modules_and_patterns+registration with test module suseconnect_scc: https://openqa.suse.de/tests/8291092#step/suseconnect_scc/26 On the other hand we have another test suite which boot a registered system with basesystem,server and desktop and unregister it and install basesystem,server,desktop,development modules with test module installation/addon_products_via_SCC_yast2 as follows: https://openqa.suse.de/tests/8292986#step/addon_products_via_SCC_yast2/35 https://openqa.suse.de/tests/8291739#step/addon_products_via_SCC_yast2/7 which has a wrong name due it has dependency in the past from some sdk test suite. As we clean the registration in the second case, with the first test case should be enough to test this functionality and we use YaST tools instead of userspace tools. We should consider to migrate to libyui REST API for this YaST module, which is also one (if not the most) used by customers. #### Acceptance criteria **AC1**: Migrate to libyui REST API yast2 scc and schedule in test suite select_modules_and_patterns+registration **AC2**: Remove test suite sles+sdk+proxy_SCC_via_YaST #### Suggestion Probably we don't have a test yet that use libyui for installation and after first boot in single test suite but it should work. Avoid to rewrite the existing old code and focus on new approach we use for installation. For opening modules in the install system we used `YaST::Module`. Be aware the code for the installed system is not so organized. Last Las part of the test probably we still need to use some needling as package selection does not work with libyui REST API. Create a new test module to avoid mixing non-libyui REST API with shortcuts/needles approach.