September 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Plan for moving to new CI
by Josef Reidinger 26 Sep '13

26 Sep '13

Hi, in SUSE workshop we start project to move continuous integration (CI) from internal server to external[1], so everyone can see how yast is tested and also can use it. For such plan there is needed in principle 4 tasks 1) create maintenance branch ( we don't want to break current OS release ) - DONE 2) replace spec templates with spec file using rpm macros ( lslezak already prepared it and we start create pr soon ) 3) use uniform commands to check, build, submit to devel BS project and submit to target BS project - here we decide to use rake and there is already project to use - https://github.com/yast/yast-rake that using https://github.com/openSUSE/packaging_tasks/ We need to test each module if it works with it ( often problem is missing license headers there ) and adapt if needed. There help is really welcome. 4) create tasks in external ci instance - there is script which will do it for us, so it will be automatic and quick. So if anything is interesting in this move feel free to contact me at IRC or via mailing list and can start playing with step 3) for any module. Josef [1] http://ci.opensuse.org/ -- 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: Merge yast-meta into yast-devtools
by Josef Reidinger 26 Sep '13

26 Sep '13

Hi, When I think about yast-meta and how we can make easy way how to do mass changes to all our yast repos I think we should benefit from yast-meta, but I think that right place for it is yast-devtools to have all tools for developers at one place. I also would like to clean devtools to contain only used tools and make it better, so we can benefit from it. Any opinions, comments or counter-proposals? Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 2

[yast-devel] Example for stubs in RSpec
by Gabriele Mohr 23 Sep '13

23 Sep '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, at the work shop we decided to use RSpec as the testing framework and I started to write spec-files for the YaST Fcoe Client. The task was to create tests for a method which calls some methods reading from system files or getting hardware info. So for the test I need return values set for these methods. This is done by using stubs. Tested method is FcoeClient::DetectNetworkCards which calls e.g. GetVlanInterfaces and GetFcoeStatus. Examples for stubs of called methods: @test_class.stub(:GetFcoeStatus).with("eth1.300", "eth1").and_return({}) @test_class.stub(:GetVlanInterfaces).and_return({ "eth1" => [{ "vlan" => "400", "fcf" => "00:0d:ec:a2:ef:00" }, { "vlan" => "300", "fcf" => "00:0d:ec:a2:ef:01" }], "eth2" => [{ "vlan" => "200", "fcf" => "00:0d:ec:a2:ef:02" }]}) The complete spec-file DetectNetworkCards_spec.rb is attached. Complete yast-fcoe-client on https://github.com/yast/yast-fcoe-client. Greetings Gabi - -- Gabriele Mohr SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstr. 5 Tel: +49 911 740 53 362 90409 Nürnberg Email: gs(a)suse.de - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFSQDfnzwhO63ql6h0RArbsAKCFMX3xIqgETzgLkEsB9nlFsrl1YACfVPDE ijio8fhWxfklP66+mAvinFw= =cIeA -----END PGP SIGNATURE-----

2 1

[yast-devel] OBS YaST:Head project: added openSUSE-13.1 build target
by Ladislav Slezak 23 Sep '13

23 Sep '13

Hi all, openSUSE-13.1 has been branched from Factory so I have added it also to YaST:Head. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- 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] Requirements for Yast testing framework
by Ladislav Slezak 13 Sep '13

13 Sep '13

Hi, in a different thread we are discussing the possible frameworks for writing tests. Although it's nice to have some preferred framework and style, we should actually collect our requirements first to see what we need or expect from it. I'd like to start a broader discussion because once we choose the framework and start writing tests then it will hard to go back and use something else... Look at the current existing Yast tests. What do you like? What you don't like? Which features you miss or need? Here are my ideas, please comment, add your expectations, requirements... Testing Framework Requirements ------------------------------ - For programmers: The tests will be written by programmers and used by programmers. Therefore we do not need any human readable language in tests (like in Cucumber [1]). That only adds one level of complexity for developers without much gain. The tests should be easy readable without strange syntax or rules. You should quickly see what is being tested and how from the test code. - Mocking Ruby calls: During tests we need to stub and mock some method calls to avoid touching the real system. We need to provide testing data as a part of tests. We need to mock any Ruby call, the current Yast is able to mock only SCR calls and that's limiting and makes troubles when using other modules. - Unit tests: We do only unit testing [2] in Yast (we test modules/methods separately without any context), so unit test support is mandatory. The question is if we could do more and also use integration testing [3] in the future. Like the installer could setup partitioning and then check bootloader and software proposal. That would probably need some UI support, but in some cases it could be nice. - Development tools integration: Currently we run "make check", the framework should be easily used from make (or rake) from Yast code. - OBS integration: We also run the tests during package build in OBS so we need to package the testing framework as a RPM package. It also needs to work in OBS environment properly (e.g. there is no internet access, no outside connection is possible). - Code coverage: To have good tests we need to know the code coverage to easily find the missing parts. - Sharing framework configuration, testing code, asserts...: It should be easy to share common parts, asserts... to avoid code duplication and make maintenance easier. - Last but not least: it should be well maintained (SLE support!), stable, well documented... (as usual with a good software...) Thanks for your comments! [1] http://cukes.info/ [2] http://en.wikipedia.org/wiki/Unit_testing [3] http://en.wikipedia.org/wiki/Integration_testing -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

7 12

[yast-devel] Yast and CI
by Josef Reidinger 12 Sep '13

12 Sep '13

Hi developers, we agreed that current CI in jenkins have some problems and I would like to face it. But at first I would like to hear your opinions on current setup, what is weak points and what is nice features we like. Few questions I have in my mind: testing: current it test only changes in master branch. How important for you if we automatic test also pull requests and maintenance branches? Related question is how important for us is to have generated <package>.spec file as it quite block more generic solutions. autosubmit: Are you satisfied with current autosubmit to Yast:Head? And what about automatic submit to factory? What is criteria to submit to Yast:Head and to factory? Do you want it automatic or some someautomatic or manual step is better from your POV? involvement: Do you want actively help with CI? ( current status is that usually I fix it myself when I see fail ) Do you have own idea what can be automatic or what can help with removing common task? openess: Problem of current status is that yast CI lives in suse network ( benefit is that we have direct access to our test machines and can easy modify it ). What about using http://ci.opensuse.org/ instance? where then must live workers? I see that cloud guys use it, so maybe we can discuss it with them (mvidner do you have closer information?)? Thanks for feedback, Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 10

[yast-devel] SUSE developers move to #yast on freenode
by David Majda 10 Sep '13

10 Sep '13

Hi, YaST is an open project -- its code is open source, there is a public bug tracker, mailing list, wiki, etc. But there was one small area where YaST remained somewhat closed -- SUSE internal IRC channel, where SUSE developers discussed YaST-related topics, coordinated code reviews, etc. Some of us recently noticed this discrepancy. After few days of discussion the SUSE YaST team decided to discard the internal channel completely and move to the public #yast channel on freenode: irc://chat.freenode.net/#yast This channel has existed before, but it wasn't used for coordinating development and in fact many developers didn't hang there at all. We hope this step will make it easier for the community members to engage with YaST developers, start contributing, or just watch the discussion and learn. It will also force us to be more transparent in general, which is always a good thing :-) -- David Majda SUSE Studio developer http://susestudio.com/ -- 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] is doxygen working for you?
by Martin Vidner 09 Sep '13

09 Sep '13

Hi, I found out that yast2-core's autodocs is populated with many files by doxygen (1.8.2-2.1.1, on 12.3) but the class index page (annotated.html) then contains only a handful of classes. OTOH file:///usr/share/doc/packages/yast2-core/autodocs/annotated.html from yast2-core-devel from YaST:Head for 12.3 is properly populated. Is it just me? Can someone reproduce this? -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[yast-devel] simple ruby client to test SCR code?
by Arvin Schnell 09 Sep '13

09 Sep '13

Hi, what is the simplest Ruby based client to test SCR code? I tried something like this: module X include Yast r = SCR.Execute(path(".target.bash"), "/usr/bin/true") Builtins.y2milestone(r) end but here path is undefined. Regards, Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

3 3

[yast-devel] git: suse-changelog-merge
by Martin Vidner 06 Sep '13

06 Sep '13

Hi, some of you complained about the conflicts that `git merge` produces for .changes files. Help has arrived! https://github.com/mvidner/changelog-chew Please try it and let me know how it fits your use cases. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0