Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Georg Tuparev <email@hidden>
- Date: Thu, 26 Jun 2003 13:28:46 +0200
Just my 0.02
I fully agree with Malte ... but he is very diplomatic ;-). Mocks are
evil! They are needed mostly in 4 cases:
- as workarounds for badly designed languages (Java, and C++ comes in
mind)
- missing middle tier frameworks or badly written ones (EOF vs. JBeans)
- Wrong application design (no orthogonal modules, violation of DRY,
etc)
- slow hardware
cheers
gt
On Thursday, Jun 26, 2003, at 08:48 Europe/Amsterdam, Malte Tancred
wrote:
There is an interest. However, after trying out mocks in a (WO
Java) project a while back I've come to feel a bit reluctant
towards them. There are situations where a mock really can help,
but I think these situations should be actively kept to an absolute
minimum. As you wrote yourself, setting up a mock might require
quite a lot of code, and keeping it up to date might be both
troublesome and tedious.
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.