On 10/02/2018 11:18 AM, Lukas Ocilka wrote:
-------- Forwarded Message -------- Subject: YaST GUI testing framework Date: Mon, 24 Sep 2018 18:37:18 +0200 From: Rodion Iafarov
To: yast-devel@opensuse.org 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.
After a nice discussion with Stefan Hundhammer and Chistopher Hofmann, we got clear that we cannot simply resurrect functionality which was there already as it's based on YCP, which YaST team wants to replace for quite a while. Our QA team feels fancy to help with the progress in order to get scalable framework for YaST GUI testing, including installer. However, as you have better insights, we need your help to decide steps to be done and split them to the items we can deliver during the sprint. This will allow us slowly moving forward.
Questions to clarify before we start:
1) Will YCP be dropped in foreseeable future, if yes what shall be used instead? yaml+ruby?
Do you mean the programming language called YCP or the components system called YCP? I'm asking because, although we usually say "YCP" to refer to that perl-ish language we are indeed dropping, YCP actually stands for YaST Communication Protocol and I would say is still the main method to communicate our Ruby code with libYUI and with WFM. Isn't it? For more fun with acronyms, check https://yastgithubio.readthedocs.io/en/latest/architecture/
2) Where to start? We could have a fork of libyui which is used for testing, or our implementation has to be secure not to introduce any new flaws
Using a separate "feature branch" sounds good as long as it does not run for two years before being merged back to master, like storage-ng. :-)
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.
Looking forward to your reply.
Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org