August 2013 - YaST Development - openSUSE Mailing Lists

[yast-devel] Fixing yast2-slide-show for SLE11 SP3
by Karl Eichwalder 16 Sep '15

16 Sep '15

I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I have to use, please? Thus far, I have checked out trunk only. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 7

[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] RFC: Drop yast2 sw_single CLI interface
by Josef Reidinger 03 Sep '13

03 Sep '13

Hi, I would like to drop yast2 sw_single CLI interface because zypper already do such job much better and if we drop it, then it simplify code and we have only one recommended solution which we need to maintain. Any comments, suggestion or complain. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

8 15

[yast-devel] unit tests for yast modules written in ruby
by Roman Neuhauser 02 Sep '13

02 Sep '13

hola! vlado brought up an interesting topic, namely the choice of a unit-testing framework. there's a bunch of them written for ruby code, some of the most popular ones (presented in no particular order) are: * minitest http://rubydoc.info/gems/minitest/frames * rspec http://rspec.info/ * shoulda http://rubydoc.info/gems/shoulda/frames * Test::Unit http://www.ruby-doc.org/stdlib-1.9.3/libdoc/test/unit/rdoc/Test/Unit.html see https://en.wikipedia.org/wiki/Unit_testing_frameworks_for_Ruby for a pretty good overview. i have no strong preference or dislike for any of them, with the exception of rspec, which creates methods on the CUT (to be clear: i don't like that). but before we dive into a massive flamewar re: which one is the best, there's another topic to chew on: do we need to standardize this at all? as far as i understand the situation, yast modules are mostly silos with one or two people ever hacking on any given module. this arrangement would lend weight to the argument that no, we don't need to standardize on a single unit-testing framework, each maintainer is free to choose whatever they like most. OTOH, strong code-ownership has its downsides, so maybe, unless we want to make the segregation of interests stronger, we should not move the code further apart. a standard test framework would make it easier to move code between modules, eg. utility functions initially written for a specific yast module getting promoted to ruby-bindings or something. opinions? -- roman -- 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] Questions about some YCP Equivalents in ruby
by Thomas Fehr 02 Sep '13

02 Sep '13

Hi, While I was just fixing a bug in current head and had to test the fix anyway I assumed I could easily modify the ruby code needing to be adapted anyway to a more ruby-like style. I replaced the common usage of hash access with default parameter by YCP Code --> Ruby like replacement part["fsid"]:0 --> (part["fsid"]||0) part["type"]:`none --> (part["type"]||:none) substring(part["device"]:"",0,9) --> part["device"][0,9] Could someone with more ruby experience tell me if these replacements are reasonable? My testing showed they work, but I am not sure if there are pitfalls I am not aware of. Tschuess, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr(a)suse.de GPG public key available. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

6 13

[yast-devel] YaST crashes selecting a few modules
by Freek de Kruijf 28 Aug '13

28 Aug '13

I did a new installation with the M4 iso and added http://download.opensuse.org/repositories/YaST:/Head/openSUSE_12.3/ as a repository. After that I forced an update of all modules in that repository. I needed to leave some "obsolete" packages in the system, but most were updated from that repository. After that I could start the YaST window, but the bootloader module and the software module did not start. Did not try other modules. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 1

[yast-devel] installer's memory requirements
by Michal Filka 28 Aug '13

28 Aug '13

Hi, i'm currently testing latest build (openSUSE-Factory-DVD-x86_64-Build06) and I'm running out of memory. Currently I use VirtualBox' VM with up to 2GB (for M3 512MB was enough). I also got: "YaST got signal 11 at YCP file /mounts/mp_0001/usr/share/YaST2/modules/Storage.rb:2343" Anyone experienced same issue? Side note: the message should be updated as YCP is not in game any longer ;-) Michal Filka -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] Rules for yast development after feature freeze
by Josef Reidinger 27 Aug '13

27 Aug '13

Hi, opensuse is already in base system feature freeze, so all features that affect installation should be postponed. I create simple wiki page[1], that describe how we can store future changes, because usually bugfixes have bigger traffic then features to it. But if we want start with some ideas how to improve installation we can do it now respecting given rules. The most important part is that also changes going to separate branch for next opensuse should be reviewed, so we prevent big branch that cannot be reviewed. Josef [1] https://github.com/yast/yast-yast2/wiki/How-to-make-changes-affecting-base-… -- 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] Unify yast-yast2 directory structure
by Josef Reidinger 27 Aug '13

27 Aug '13

Hi, now yast-yast2 contain library directory that is separated to sub-directories [1]. I would like to have there only one src directory that respect Y2DIR structure. Main benefit from this move is that it is much easier to test code, because now there interdependencies between directories, so you need to know what subdirs you must use and it means you must create a lot of effort to detect it or test only on installed system ( both is bad from my POV ). The biggest drawback is that we lost logical separation between these modules, but we can improve documentation, so it is not so big ( like links in documentation of related modules ). Do you have any objections, opinions or comments? If not I do it on Tuesday 27th ( so lslezak and mvidner can make comments after his return from vacation ). Josef [1] https://github.com/yast/yast-yast2/tree/master/library -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 3

[yast-devel] ldap Viewer cn=Administrator
by Günther J. Niederwimmer 27 Aug '13

27 Aug '13

Hello, Can any tell me on witch place the ldap-Viewer store the cn=.... I have installed my ldap with a other "cn=admin" but the ldap-Viewer don't read the /etc/sysconfig/ldap and I have always the "cn=Administrator" This is a SLES 11 SP3 system. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

2 2