Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Michael Tsai <email@hidden>
- Date: Wed, 25 Jun 2003 16:38:12 -0400
On Wednesday, June 25, 2003, at 12:50 PM, James Quick wrote:
Before I invest more time in learning about them, I would like to know
if anyone on this list is actively using either of the tools as part
of their
regular workfow?
Both seem to be good tools. I chose ObjcUnit because its approach of
using a separate target seemed to make it easier to keep test code
separate and to only run the tests when I want to. OCUnit's integration
with the Project Builder error list is slick, but I found that I
preferred the JUnit-style text output. Also, OCUnit's macros conflicted
with Objective-C++ (not sure whether that's still the case), which I
was using at the time.
ObjcUnit also has some pre-build mock classes, which you may find
useful. My main complaint about it is that the JUnit-style methods for
assertion are very verbose. I wrapped them in macros that stuff
__FILE__ and __LINE__ into the message string so that I can easily
figure out which assertion failed.
--
Michael Tsai <
http://www.c-command.com>
_______________________________________________
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.