Dne 02. 10. 18 v 11:18 Lukas Ocilka napsal(a):
> -------- Forwarded Message --------
> Subject: YaST GUI testing framework
> Date: Mon, 24 Sep 2018 18:37:18 +0200
> From: Rodion Iafarov <[email protected]>
> To: [email protected]
>
> Dear YaSTees,
>
> I would like to kindly ask for your help. In order to make next game
> changing step for YaST GUI testing, we need to improve macro player
> functionality.
My first question would be: is the macro player good enough?
If we want to invest some time in this area, maybe we could use
something else.
> In case we cannot get enough support and development is too heavy, we
> may use squish or ldtp, which have certain limitations, but will server
> the purpose.
I have spent two hackweeks developing an automatic YaST UI testing
framework. It's based on a REST API (HTTP with JSON format), it can not only
send the user input actions but can also test the content of the
current dialog.
The advantage is that the REST API is not bound to any programming language,
you can write a client driving an YaST installation in any language. With help
of
"curl" and "jq" it would be possible even in shell... (but I'd avoid it)
The YaST UI actions which can be done by user are quite limited (e.g. you can
press a button, select a checkbox, write something to an input field... and
that's basically it). So made a simple Cucumber wrapper which defines such
steps.
Of course, if you do not like Cucumber you can use any other framework, you
could extend the current openQA or start something new from scratch. That's
a big advantage of the generic REST API, if the testing frontend does not
fit any more you can easily change it without affecting YaST itself. We could
even
use a different frontend in our CI (Travis/Jenkins) and different one in
openQA built on top of the same REST backend.
See more details about the REST API in my hackweek blog posts [1], [2].
If you want to give it a try I have prepared RPM packages for SLE15/Leap15
in [3], how to install the packages is described in the Cucumber wrapper
at GitHub [4].
(Note: I built the packages several months ago, if something does not work
now just ping me.)
This project is far from complete, there are still some missing parts
like support for some specific widgets, security improvements (authentication
and encryption, isolating to a separate plugin so the REST API can be installed
only when needed, not included in the default installation, etc...).
But the prototype is already able to test the default openSUSE/SLE installation
well,
(see the screencasts in the blog) so I think it would make sense to at least
think
about this possibility as an alternative to the UI macro player.
If you have any questions about this project just ask me.
Note: Because this REST API is available for any libyui application and is not
YaST
specific we could possibly cooperate with the Mageia (formerly Mandriva,
formerly
Mandrake) developers, their management tools also use the libyui [5] and having
a
testing framework would probably help them as well...
Ladislav
[1] https://blog.ladslezak.cz/2018/07/13/hackweek-17/
[2] https://blog.ladslezak.cz/2017/12/06/hackweek-16-yast-ui-rest-api/
[3] https://build.opensuse.org/project/show/home:lslezak:libyui-rest-api
[4] https://github.com/lslezak/cucumber-yast
[5] https://madb.mageia.org/package/show/name/manatools
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: [email protected]
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
