action #113731
Updated by JERiveraMoya over 2 years ago
#### Motivation ##### The only test module stopping us to move to libyui REST test suites in MUs is `installation/add_update_test_repo`. Although we will favor to add a DUD for adding maintenance updates (see #113734) we should have available this iterative solution to add add-ons during the interactive installation with libyui REST, in case we need to fall back to it, due to the DUD solution would require a chained job which might fail for some reason (but it should be fine, just thinking in the worst case scenario). #### Scope #### SLE-15-SP{3,4}, where we can use libyui REST, but we can start applying only to one test suite for example. #### Acceptance criteria #### **AC1**: An equivalent test module to [installation/add_update_test_repo](https://openqa.suse.de/tests/9157419#step/add_update_test_repo/1) using libyui REST is created. #### Suggestion We could add a name for the repo in similar fashion we did for AutoYaST, it makes easier to identify the repos and with libyui REST we can be in the safe side even when more typing is provided. **** draft **** add_update_test_repo