Mailinglist Archive: yast-devel (79 mails)

< Previous Next >
Re: [yast-devel] Rspec as specification: Cucumber
On Wed, Mar 02, 2016 at 11:14:42AM +0100, Josef Reidinger wrote:
On Wed, 2 Mar 2016 11:06:57 +0100
Arvin Schnell <aschnell@xxxxxxxx> wrote:

On Tue, Mar 01, 2016 at 05:16:49PM +0100, Martin Vidner wrote:
On Tue, Mar 01, 2016 at 04:53:41PM +0100, Josef Reidinger wrote:
as there is in last days some discussion how rspec can be used as
specification or not and I would like to document how bootloader
do its proposal, so I take it as oppurinity to write it in RSpec.

Output for better formatting is placed to pastebin

Please ignore for now typos. I am more interested if it is
readable for you as specification how bootloader is proposed.

Yes, it is a good summary of the requirements!

No, these do not look like requirements but as *one*
solution. Requirements should include the motivation.

Yes, it is not requirements, it is specification how it works.
Requirements and explanation why something is done in given way is
captured in comments in code. Specification only say what it do, not

I see. As specifications go, RSpec is fairly low level I think.
Would it be useful to use something higher level, for example
Cucumber? It focuses on descriptions readable by non-programmers
which are transformed into code and executed as tests.

Here is an example for Zombie Killer: a runnable document (not using
and a Cucumber version in the evolved ZK, Rubocop-Yast:

(sorry, the examples do involve code because that is the object of
the zombie killer)

Martin Vidner, YaST Team

Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
< Previous Next >
Follow Ups