December 2012 - YaST Development - openSUSE Mailing Lists

[yast-devel] Disturbing branches at GitHub (broken/...)
by Lukas Ocilka 22 Mar '13

22 Mar '13

Hi, You've probably already found out that there are a lot of "broken" branches at our GitHub repositories: For instance: * upstream/broken/master * upstream/broken/openSUSE-10_0 * upstream/broken/openSUSE-10_1 * upstream/broken/openSUSE-10_2 * ... AFAIK, these branches were left there from the unsuccessful migration from SVN to GitHub. So, what are we going to do with them? From my point of view, they are not needed and just disturb there. Thanks in advance Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 10

[yast-devel] yast mocking module - problem with replacing function
by Josef Reidinger 12 Dec '12

12 Dec '12

Hi Yast Hackers, as part of my attempt to improve testability of yast code, I hack on mocking module. My goal is to allow writing test code in ruby ( that contain cool testing frameworks ) and only missing part is mocking, because I need to mock it in ycp ( or other bindings ) and stubba works only on ruby code. My code ( in non-working state ) is available at [1]. Everything works, except that it doesn't work :) To give overview I create mock stub call and that deploy proxy component, namespace and function. All parts just provide hooking and if it is called with interesting call, then it replace evaluation with stub result. I write also test case to verify it and it doesn't work ( to work, it needs modified yast-core which allow component replacement in ComponentBroker and Import and git version of ruby bindings that contain fix for camel case ycp modules ). Problem from debugging looks like inside ycp bytecode that preresolve namespace evaluation and calling component broker or Import is not take in effect. Am I right? Does anyone see what is wrong and if it is at all possible to implement it? Thanks for any response Josef P.S. If it looks good, I would like to include it also to SP3 and allow easy unit testing for our fixes for SP3. [1] https://github.com/jreidinger/yast-mock -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] RFC: Automated tests for AutoYaST (for yast2-network)
by Martin Vidner 12 Dec '12

12 Dec '12

Hi! Michal and I are working on a bug with network configuration using AutoYaST. The fix is rather intrusive so we want to add tests and check for regressions. The basic idea for such tests is to start with a specific AY profile and a matching virtual hardware (network cards), run the installation, and check the resulting filesystem for expected configuration. One test case: - autoyast profile - feature being tested (eg. NIC naming) - helpers for the automated test (multiple pkg repos, disable sig check, final_halt) - a standard installation repo (SP2) - new yast package(s) to test - to be put to a DUD and an add-on repo (on a CD) - virtual hardware configuration (platform: libvirt) - feature-wise (number of NICs and their MACs) - helpers (second CDROM) - assertions to check after the run - simple way: check that some files have excactly some expected content Automating multiple runs of multiple test cases: TBD If this sounds too abstract, here's our existing manual test plan for the bug: http://idontknow.suse.cz/install/ (internal, hrefs work) https://gist.github.com/4194824 (external, hrefs broken online) AFAIK we don't have a framework for such tests, so we want to build one. Well, I know of some related work: - OpenQA - Hamsta - Jenkins CI - AutoYaST tests that I don't know of? So that's why I'm sharing the design and want to check with you: Are we reinventing the wheel? Can we reuse the existing projects? -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

3 2