[rspec-users] be_none and be_any don't seem to work properly

David Chelimsky dchelimsky at gmail.com
Wed Oct 21 11:45:07 EDT 2009


On Oct 19, 2009, at 2:12 PM, iain wrote:

> Hi all!
>
> I'm testing some named scopes. I use be_all(&:some_predicate) to test
> if all the elements in the collection are valid, which works, but when
> I try to test the inverse, it fails.
>
> You can see the complete code at: http://gist.github.com/213636
>
> But in short:
>
> subject = User.active
> subject.should be_all(&:active) # works
>
> inverse = User.all - subject
> inverse.none?(&:active).should be_true # works
> inverse.should be_none(&:active) # doesn't work
>
> And also "inverse.should_not be_any(&:active)" doesn't work either
>
> And I cannot figure out why. The RDoc of rspec or rspec-rails don't
> mention be_none or be_any, so I would think that this would be
> straightforward. Anyone any ideas?

I'm not certain, but I _think_ that the problem is the way you're  
setting up the factories. Try just creating the objects directly and  
see what happens:

http://gist.github.com/215201

HTH,
David



>
> Thanks in advance,
> Iain - iain.nl
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

Cheers,
David





More information about the rspec-users mailing list