action #36712: [sle][functional][y][yast][hackweek][saga] Use YaST specific framework for GUI testing
[functional][y][epic] Automate yast2 hostname test suite using YaST framework which is not relying on shortcuts
|Category:||Enhancement to existing tests||Estimated time:||13.00 hours|
|Target version:||SUSE QA tests - Milestone 22|
As an outcome of #37324, we should start with simpler things to get results before investing to much time in the long-term solution due to missing details.
yast2 hostname is one of the simplest test modules, the only missing functionality from YCP testing framework is work with tables.
Therefore, first task would be to implement this functionality in libyui for ncurses/qt/gtk first and then extend it.
- yast2 hostname is tested using YaST specific GUI testing framework
We already have many parts included in YCP, which can be reused, but technical solution should take into consideration that it may get dropped and replaced with ruby,
so framework has to be extended in that way, that these parts can be reused. Consult with YaST team about the details.
#19 Updated by riafarov about 1 year ago
- Status changed from New to Rejected
- Assignee set to riafarov
@riarafov could you please help link this epic without any left open subtasks accordingly to the other tickets referenced in the parent ticket? Or would you also reject this one in favor of the others?
To be honest, I considered rejecting it when I saw it, as it considered completely different strategy. I still believe hostname is a good candidate to start with. But let's reject it for now.