action #116500
Updated by JERiveraMoya over 1 year ago
#### ## Observation seems like test needs to be updated, to choose do not start in listbox and then update needle afterwards. openQA test in scenario opensuse-15.5-DVD-aarch64-yast2_ncurses@aarch64 fails- - Problem on Leap 15.5: [yast2_dns_server](https://openqa.opensuse.org/tests/2646586/modules/yast2_dns_server/steps/57) - Problem on SLE 15 SP5: [yast2_dns_server](https://openqa.suse.de/tests/9565297#step/yast2_dns_server/53) Fails since... - Fails since (at least) Build [277.3](https://openqa.opensuse.org/tests/2645811) on Leap 15.5 - Fails since Build [24.1](https://openqa.suse.de/tests/9565297) on SLE 15 SP5 Apparently current code cannot work: ## Scope https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/yast2_widget_utils.pm#L78 So basically when it works, like in TW is because we are losing the up key, afir there was a modification for `send_key_until_needlematch` which force always to send the key until needle match, when before if the needle match it wasn't sending any key. Nevertheless, rather than fighting with needles we can create new test module using libyui-rest-api. - Yast Review ## Acceptance criteria **AC1**: Create new test module which does similar actions and uses libyui-rest-api. **AC2**: Enable this test modules in all the places where **AC1:** Test is failing indicated in this ticket. **AC3**: When designing Pages and Controllers follows existing code convention. **AC4**: For test design, open module, do some action, close module and validate via command line (do not validate with libyui the screen like we do with needling). **AC5**: Encapsulate functionality to change service from #113492 so we can reuse the code for this bits. fixed ## Additional info Problem was first reported for Leap 15.5, but is also occurring occuring on the latest SLE 15 SP5 build. We will be mapping screens, creating pages and controllers in similar fashion than #113492 Notice that design is based in doing certain actions in the UI with libyui (without checking the screens with libyui rest api, just the navigation) and then close the module and do the validation with command line. It is very similar to the behavior of this existing test module.