> > The way to do the "Skippy" thing under RSpec 2 will be filtering: > > http://blog.davidchelimsky.net/2010/06/14/filtering-examples-in-rspec-2/
Awesome! Just what i need :) > > Generally, the trade off between "explicit" and "DRY" is different in specs > than it is in code. In specs we value explicitness and simplicity above > DRYness (the specs have to be bug free, they have to be readable, they should > be a document -- ie. a specification -- of the behavior of the code, and > perhaps most importantly of all, you want to be able to click on a failing > spec's file and line number and be taken straight to it and know which spec > failed without any ambiguity) whereas in code DRYness is given a much higher > value. > > So I don't know how many entires you have in your > STATUS_EXPECTED_TRANSLATIONS, but if the number is small enough, I'd suggest > that you just list the translations explicitly, repeating the "it" block for > each translation. > Thank you for your advice! It makes sense to me, and the list of options is indeed limited ;) _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
