Raymond Barlow wrote:
...
>
> Oh, and another question, is the above command the correct thing to run
> to
> see the examples run? And if so, do I run it in examples/simple or
> examples/simple/features?
>
> /Raymond
>
> 2009/5/18 Trond Marius Øvstetun
Hi Raymond. Did you get it to run on you
Hi David,
On 29 May 2009, at 12:10, David Chelimsky wrote:
Have you read "Mock Roles, not Objects"?
"its corresponding mock" suggests a single mock object for each real
implementation. There's nothing stopping you from writing your own
mock objects to play this role. IMO, this is not what a dyna
On Fri, May 29, 2009 at 6:26 AM, Diwakar, ANGLER - EIT
wrote:
> -- Controller
>
> def create
>
> �...@avatars = Avatar.find( :all,
> :conditions => { :user_id => 0 }
> )
>
> @avatars.concat( user.avatars )
>
> end
>
>
> --- spec ---
>
-- Controller
def create
@avatars = Avatar.find( :all,
:conditions => { :user_id => 0 }
)
@avatars.concat( user.avatars )
end
--- spec ---
describe UserAvatarsController do
describe :create do
before(:each) do
@a
Hi Tom,
On Fri, May 29, 2009 at 4:11 AM, Tom Stuart wrote:
> Hi,
>
> One of the problems with mocks, as far as I can tell, is that they might go
> out of sync with the real object they're mocking.
Have you read "Mock Roles, not Objects"?
http://mockobjects.com/files/mockrolesnotobjects.pdf
> I
Hi,
One of the problems with mocks, as far as I can tell, is that they
might go out of sync with the real object they're mocking. Is it
possible and sane to detect this by running each spec against its
corresponding mock? Does anyone already do this?
For example: your Account object has a
