Dne 3.3.2016 v 10:33 Ladislav Slezak napsal(a):
The problem is that you have to maintain the intermediate part which translates the specification into executable Ruby code. If your tests are too different you need to maintain many transformation rules.
BTW if you are interested in the rubocop-yast transformations see [1]. This file converts the specifications into executed Ruby code (RSpec expectations in this case). For rubocop-yast there are just few transformations, I'm afraid that for usual YaST modules it would blow up into a big list... [1] https://github.com/yast/rubocop-yast/blob/master/features/step_definitions/c... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org