[dev] [commits] Horde branch master updated. 3d5433806251d1e14d73fb2f5abf8347cf07389d

[Michael M Slusarz]

Quoting Michael Rubinsky <mrubinsk at horde.org>:

> FWIW, I've had similar experiences. My experience with PHPUnit mocks  
> is also limited, mostly in the ActiveSync tests, but I found them  
> very hard to work with and found that the majority of my test  
> failures were due to incorrect mock definitions. I was also spending  
> more time debugging the mocks than I was spending on any other part  
> of the testing process.  I finally got what I wanted, but I feel  
> they are very fragile. Unless we really need some functionality they  
> provide, such as specifying the number of times a method should be  
> called etc..., IMHO, we should stick to using stubs, except maybe in  
> the most simplistic cases.

Guess I am confused, because this is one of the main reasons to use  
*mocks*, not stubs, since stubs are the one that require constant  
maintenance.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]