[rspec-users] New RSpec methods to Object proposal: should_all and should_none

David Chelimsky dchelimsky at gmail.com
Wed Dec 9 08:27:43 EST 2009

On Wed, Dec 9, 2009 at 5:41 AM, Rodrigo Rosenfeld Rosas <
lbocseg at yahoo.com.br> wrote:

> I was thinking that it would be great to add 2 additional methods to
> Object: should_all and should_none.
> The idea is that we would be able to write tests like:
> [@admin, @allowed_user].should_all be_allowed_to_visit(url)
> [@unprivileged, @non_welcome].should_none be_allowed_to_visit(url)
> Implementation is trivial, but I think that tests would become much cleaner
> than:
> [@admin, @allowed_user].each{|u| u.should be_allowed_to_visit(url)}
> Any thoughts on that?

How about:

each_of(@admin, @allowed_user).should be_allowed_to_visit(url)
none_of(@admin, @allowed_user).should be_allowed_to_visit(url)

This gets the cleanliness without adding to Object.



> Rodrigo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20091209/edaafec8/attachment-0001.html>

More information about the rspec-users mailing list