On 11/08/2018 10:30 AM, Rodion Iafarov wrote: > > On 11/8/18 9:52 AM, Ladislav Slezak wrote: >> Dne 07. 11. 18 v 16:39 Christopher Hofmann napsal(a): >>> Hi YaSTees! >>> >>> I had a deeper look into Ladislav's REST API and I found it very >>> flexible and easy to use - and furthermore very straightforward and easy >>> to enhance. >> The advantage of the REST API is that it's not bound to any specific >> language or >> testing framework, you can easily write a small wrapper for >> rspec,cucumber,... or >> openQA ;-) >> >>> It looks as the most promising approach for using it in openQA for >>> testing YaST. >> Great! Thank you for looking into it! >> >>> Now the question raises how we can proceed with it and what we actually >>> need to do to get it integrated in YaST's master branch. >>> >>> The benefit we get when integrate it in mainline YaST is that we are >>> able to test an testing unmodified YaST as it also is shipped to the >>> user. Testing a modified system is not really useful as it may behave >>> different to the unmodified system. >> It should be part of the system, patching the installer for testing is >> not a nice >> solution. > It's not perfect solution, but if we keep fingerprint small and validate > system without patch to mitigate the risks of missing something which > works with the framework, it's fully acceptable practice. For example, > selenium web-driver is not exactly same as user's browser, on top > actions simulation also bypasses some layers of the user action. We > cannot support testing which is repeating customer setup 1 to 1, and > even with openQA we don't. If you've seen set of bootloader options we > use, it's enough to argue that we already don't have user like setup.
Definitely I would sleep much better if the API is not available in the final vanilla (open)SUSE system. I don't mean "not activated", I really mean "not available". If it's there, it may happen that we introduce a bug that would activate it inadvertently. In case we simply decide to ship it, but deactivated by default. We should ensure the mechanism to activate it is not trivial. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
