Dmitriy,
nice to hear that there are more teams outside of YaST / SUSE that found
our tools useful.
On 2023-07-25 19:40, Dmitriy Zakharov wrote:
Hello YaST Team,
My name is Dmitriy Zakharov, I work as QA engineer for OpenText.
Our team is looking for an existing framework/tools that will allow us
to automate testing our yast modules. While researching we came across
libyui test framework that you have developed. We'd like to thank you
for the framework, the team really likes it since everything can be
done via REST API. When working on proof-of-concept we were able to
automate few tests when starting yast module(e.g. sudo Y2TEST=1
YUI_HTTP_PORT=9999 yast2 host). However, when we tried to start yast
in main mode without specifying any module (e.g. sudo Y2TEST=1
YUI_HTTP_PORT=9999 yast2) we could not navigate menu. We are using
select action but that doesn't seem to work. Please see screenshots
below for more details.
The solution to this is probably simple:
The YaST Qt control center is a very simplistic Qt program that is no
more than a launcher for YaST modules. But since it's so simple, it's
not using libyui at all, just pure Qt.
The YaST NCurses control center, however, is a libyui-based program (out
of sheer necessity because pure NCurses is too simplistic to do this).
The net effect is that you can't use the REST API with the YaST Qt
control center. And it will probably be problematic with the NCurses
version since it's a completely separate process, and handing over
information between it and a YaST module might not work. That was always
a known limitation of our REST API.
Your safest bet is to not do your testing starting with one of the
control centers, but starting the YaST module / libyui application
directly that you want to test.
Kind regards
--
Stefan Hundhammer <[email protected]>
YaST Developer / libyui + libyui-qt main author
SUSE Software Solutions Germany GmbH
GF: Ivo Totev; HRB 36809, AG Nürnberg
