-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, is there a decision about the prefered test framework yet? Reading this tread and the thread about Requirements for YaST testing framework, for me it seems that 'minitest' has slight advantage. And I think it is agreed that all YaST modules should use the same frame work (as far as possible). Greetings Gabi Am 08.08.2013 17:37, schrieb Roman Neuhauser:
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?
- -- 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@suse.de - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFSJGI0zwhO63ql6h0RAhNsAJ4qc3OzD1PRh32turuVRMv6pGvDowCdGPuH KLH10Cc+wYVPRAfVSVmS3ww= =JEa0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org