Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Malte Tancred <email@hidden>
- Date: Thu, 26 Jun 2003 08:48:06 +0200
Michael Tsai wrote:
Actually, it looks like MockCoder is the only one implemented in
ObjcUnit so far, but at the time I started using it, it looked as
though there was interest in creating more mock objects for AppKit,
which would make it easier to test controller classes.
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.
Also, the initial cost of writing a mock is a lot greater than
simply writing a test. You often have to write quite some lines of
code before the mock is ready to use, and those lines of code are
untested.
So, mocks should be used with care.
Cheerio,
Malte
--
Malte Tancred
Computer Programmer
Oops AB,
http://oops.se/
_______________________________________________
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.