[rspec-users] something.should_be_open blows up?
aslak.hellesoy at gmail.com
Tue Dec 19 12:32:11 EST 2006
On 12/19/06, Pat Maddox <pergesu at gmail.com> wrote:
> context "A new Foo"
> specify "should be open" do
> ArgumentError in 'A new Foo should be open'
> wrong number of arguments (0 for 1)
> class Foo
> def open?; true; end
> What's the deal with that? I looked in the RDoc and nothing seems to
> define open?. I can get around it for now by doing the opposite
> (should_not_be_closed), but that seems sorta weird. Anyone else have
Looks like a bug. A patch or bug report would be great.
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users