On Thu, 4 Oct 2018 09:06:19 +0200 Rodion Iafarov <[email protected]> wrote:
> > On 10/3/18 10:27 AM, Ancor Gonzalez Sosa wrote: > > 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 <[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. > >> > >> 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 actually meant both, as my understanding was that Communication > Protocol is also a subject to change. > Well, for communication protocol I worry it is very very long term goal, as it is just data structures which can be in future replaced by direct ruby structures or something like DBus which has own data structures that is language agnostic. ( or rest API as lada mention ). So drop of language is actually almost done, but drop of communication protocol is in very far future. > In general, it doesn't matter what will it be, my main motivation is to > find solution which fits all our needs. Can you write down all your needs? It would be good to have it written down with some use cases, so we can document it and also regularly check if it is still true and if we are heading towards it? Josef -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
