Do everything in Java…

[deadalnix via Digitalmars-d]

On Friday, 5 December 2014 at 15:28:36 UTC, Chris wrote:
>> This is very true. Specially when mocks come into play, 
>> sometimes test become duplicated code and every time you make 
>> changes in your codebase you have to go and change the 
>> expected behaviour of mocks, which is just tedious and useless.
>
> Thanks for saying that. That's my experience too, especially 
> when a module is under heavy development with frequent changes.

I second this, too much mock is a lot of work down the road.