On Wed, Jan 6, 2010 at 7:15 PM, Ben Fyvie wrote:
> We seem to be hitting some undesirable behavior with should_not in
> combination with matchers that accept collections. Let me use the “include”
> matcher for example (a co-worker reported similar problems using “be_any” so
> I don’t believe this
We seem to be hitting some undesirable behavior with should_not in
combination with matchers that accept collections. Let me use the "include"
matcher for example (a co-worker reported similar problems using "be_any" so
I don't believe this is limited to "include"). The RDoc states:
Passes if a
