I have created an updated example, the issue I am seeing happens when
any method has been included into a class from a module. It doesn't
get re-added like methods that have been inherited or added directly
to a class are.
http://gist.github.com/22159
I've updated the ticket as well, but I think
> Hey Jim - I think this is related to this:
>
> http://rspec.lighthouseapp.com/projects/5645/tickets/589
>
> Would you kindly add your comments to that ticket?
>
I updated the ticket, thanks David! I also changed the title to
something more general then the existing case implied. It's not just
Ke
rror
happens under 1.1.11 and also edge RSpec from github. We are seeing it
on Mac 10.5 and also Ubuntu 8.04.
[EMAIL PROTECTED]:~/sites/cpi2/spec/models(master)$ spec -v
rspec 1.1.11
[EMAIL PROTECTED]:~/sites/cpi2/spec/models(master)$ ruby -v
ruby 1.8.6 (2008-03-03 patchlevel 114
>> I just got back from RailsConf, and upgraded on of my development apps to
>> 2.1, and now autotest is going into an infinite loop. It runs tests
>> continuously instead of waiting for files to be saved before rerunning.
>>
>> Has anybody else seen this, or know how to get around it?
I had this
> I'm 99 44/100% sure that you have it right. The expression x != y is
> syntactic sugar for !(x == y) much like x += y is syntactic sugar for
> x = (x +y)
>
> The parser turns these into an internal representation (abstract
> syntax tree for 1.8, byte-codes for 1.9) which is identical to the
> se
> Yeah, this is fine for a simple mixin with only one shared behaviour,
> but the problem is that a real chunk of mixed-in functionality will
> probably need many behaviours that correspond to different initial
> states (provided you're behaving yourself and not doing too much state
> setup within
> > Can you show some of your code that needs to be tested?
>
> Actually, we'd hope that the code doesn't exist yet. This is Behaviour
> DRIVEN Development, after all.
>
Old habits, my apologies.
___
rspec-users mailing list
rspec-users@rubyforge.org
ht
>
> I need to write the testcase for fileimport.
>
Can you show some of your code that needs to be tested?
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
lish!
@model.should be_published
end
end
end
I can post more if that's unclear (showing the actual AR classes and
mixin), but it seems to work well and eliminates duplication. I hope
the formatting on this comes through...
Jim Lindley
http://jimlindley.com
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
