action #108227
Updated by JERiveraMoya over 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 YaST module 'yast2 scc' to libyui REST API 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, still please remember that we do some adjustments when we create image for libyui (ports, etc.) which in the installed system might be needed as well. - 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. - Instead of re-register with command line tool, we have in the YaST module button "Register again". - Last part of the test probably we will 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. - Notice that after package selection which cannot be done with libyui, a class YPackageSelector will appear there not allowing instrospection, we will get to "Installation summary" which we can automate with libyui and check the summary using Mojo lib to parse hmtl and perhaps some additional regex, like we did recently for partitioning proposal.