Re: [rspec-users] Fwd: Issue with AR::Base descendants with certain argument

e(:all) block prevents the failure, but as I said it's only here as a "shorthand" for the complex specs I have on my app. Actually declaring a .foo class method on Settings also makes it pass, so method_missing seems to be part of the problem. On my app's specs, I found out that ca

Re: [rspec-users] Fwd: Issue with AR::Base descendants with certain argument

se instead of Settings. I'll try to reproduce this within rspec-rails' own specs. -- Bira http://compexplicita.wordpress.com http://compexplicita.tumblr.com ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users

Re: [rspec-users] Fwd: Issue with AR::Base descendants with certain argument

essage for ActiveRecord::Base". I tried to reproduce this on rspec alone, but there things seemed to work perfectly. So it looks like rspec-rails plays a part on this as well. I'll see if I can reproduce it there. -- Bira http://compexplicita.wordpress.com http://compexplicita.tu

[rspec-users] RSpec-Rails 1.2.2 and Controllers without views - what to do?

consisting entirely of a single "<%= @obj.to_xml %>" line? -- Bira http://compexplicita.wordpress.com http://compexplicita.tumblr.com ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users

Re: [rspec-users] Writing specs for AMQP clients.

David and Ben, Thank you very much for your advice :). -- Bira http://compexplicita.wordpress.com http://compexplicita.tumblr.com ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users

[rspec-users] Writing specs for AMQP clients.

tives I saw for writing specs were starting said server, and mocking/stubbing out all the code that would talk to it. I went witht he second one, but I feel it's a fragile approach that won't actually allow me to find bugs, since everything is mocked out. What is the best

[rspec-users] RSpec-Rails bug with to_xml?

even weirder: the "expected" site of the assertion shows a string composed of the XML out put concatenated to itself, and the "got" side has the correct output. Something like "Expected 'aa' but got 'a'". Wha

Re: [rspec-users] Can you explain this code to me?

ffect specified in the "should" call. And from that I can determine by looking at the two incantations you posted, the lambda is used because the code can throw an error, and the spec's author didn't want the first error to prevent the outer "should" from being checked