[saga] Use YaST specific framework for GUI testing
YaST already has mechanism which may help us to develop more scalable tests using widget IDs instead of needles.
Some parts got broken meanwhile and even simple installation doesn't work when just clicking next.
Idea is to automate one test suite which we already have in openQA and evaluate if it is faster/scalable/easier to maintain/etc.
One of candidates can be yast2_gui/yast2_hostnames.pm . It will require improvements in widgets handling that we can select rows in the table.
- AC1: Simple YaST module test is automated using GUI framework which is not relying on needles and shortcuts
Conclusion and future steps
Defined goal was reached, pop-up approached was implemented and integrated with openqa to prove the concept. Here is link to the branch with changes: os-autoinst-distri-opensuse During the project I've learned more about yast gui internals. This functionality can be used in the tests with constantly changing keyboard hotkeys in first place.
After seeing this possibility to have more stable tests using yast gui internals, we can use advantage of it and stop relying on needles and keyboard shortcuts. After that I was introduced to YCP functionality which is there for a long time and already has a recorder and a player. Documentation for the Yast Programming language can be found here. This functionality can be used for testing and already contains the functionality to read widget properties and set them, as well as interact with them simulating user input.
YCP macro can be executed when application is started by simply calling: /usr/lib/YaST2/bin/y2base ./HelloWorld.rb qt --macro macro.ycp Or, it can be also called during the run using ctrl-alt-shift-p key combination and then selecting ycp file.
This part makes it possible to operate on lower level and hence make automated tests more stable and scalable.
- Usage of widget IDs allows to write tests which are resistant to fonts and layout changes
- Usage of YCP allows to avoid synchronization issues (when some control is not yet shown, but we try to act on it)
- YCP allows to avoid send keys problems we experience in openQA
- Reduced execution time as we are able to set controls property to certain value instead of typing
- Macro recorder allows to partly reduce test code development
- Tests developed in this way can be easily executed by developers and significantly reduce feedback cycle
- Can be combined with needle matching approach
- Easy migration to the solution (e.g. only newly or unstable developed tests are developed using YCP)
- Learning curve for test developers
- Missing functionality and requires further development (e.g. not possible to verify values in the table or select row with certain cell)
- Unstable behavior if used with installer (unfortunately due to some bugs installer may crash during macro execution, some trivial actions like pressing button may not work if change installers page, etc.)
- Missing openQA integration (even though it's easy to run such a test, and log errors in y2log file, the results won't be parsed and displayed in friendly way on the dashboard)
- Works only with Yast GUI, so usage scope is limited
All the disadvantages are mainly caused by the fact that YCP is not widely used, but that can be solved with reasonable time investment. In order to prove benefits of the solution we could implement one of unstable tests using YCP and run them in parallel to calculate time spent on maintenance of both solutions.
#2 Updated by okurz over 3 years ago
- Description updated (diff)
- Due date set to 2018-07-03
- Category set to New test
- Target version set to Milestone 17
I guess you would be happy to do it soonish so let's do it, doesn't have to be hackweek because you can reserve hackweek for even more fancy, new, crazy ideas :)
#3 Updated by riafarov over 3 years ago
I guess we should convert it to the epic and schedule first parts to the next sprint. In general, if one person will spend 2 full weeks on that, we will be able to fulfill acceptance criteria. And for sure next sprint(s) is a good idea not to get stuck in test fixing phase again...
#11 Updated by okurz over 3 years ago
I like the idea of a saga however what I think would be even better if we find a new saga instead which does not prescribe a technical solution, e.g. does not mention YCP but rather something about workflows, team compositions, new focus areas, improvement of product development workflows related to the yast team etc. If you think we only need a saga because a subticket is an epic: I don't have a problem with using epic on multiple levels, we already do that in other cases as well. So it could very well be something like: saga -> epic -> epic -> story
#15 Updated by okurz about 3 years ago
- Status changed from New to Blocked
- Assignee set to okurz
- Target version changed from Milestone 22 to Milestone 24
I think currently the subtasks describe in details what is workable for the next time so tracking the saga as "blocked" by the subtasks. Depending on when we would have them done setting the target version accordingly.
#31 Updated by szarate over 1 year ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html