Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Malte Tancred <email@hidden>
- Date: Thu, 26 Jun 2003 08:32:07 +0200
James Quick:
I have recently decided to try out test driven development.
Great!
For objective C testing frameworks I found two projects:
OBJCUnit - http://oops.se/objcunit/
and OCUnit - http://www.sente.ch/software/ocunit/
I have read the limited documentation available for each,
As Marco points out, there's really not much to add. The ins
and outs of unit testing is covered in great detail at various
sites.
As for ObjcUnit, maybe because it's not as mature as Marco's
(Sen:te's) OCUnit, setting up a test target is about all you
do at the moment. The rest is a lot like using JUnit. ObjcUnit
covers the classes from the package junit.framework and
junit.textui. That's about it. The JUnit documentation might
be the best place to go.
It seems that they each have a different intended style of integration
with Project Builder. OBJCunit wants to be used by defining an
additional target in PB, requiring that all your own classes to be
tested be added to that target as well as the primary. The benefit
seems to be that you can produce your real target free from any
testing code. OCUnit, provides hooks to test Objects in the interface,
and also provides hooks for testing frameworks and bundles.
OCUnit is a more mature testing kit, and there's really nothing
stopping you from creating a special test target to keep your
tests separated from the "real thing". That's my impression at
least.
ObjcUnit is (at the moment at least :-) more light-weight and
might for that reason be easier to work with in some situations,
harder in other.
You'll have to decide yourself.
The last release of OBJCUnit was v 1.2 in March of 2002. OCUnit,
has been modified every few months up until recently, but still
contains a number of components which need work or are still
using PB.proj WOProject files.
ObjcUnit is very much alive and yes, we haven't updated it in quite
a while. We have a few thoughts about coming versions, but the
problem is 1) there both have been and still are more pressing
needs on our schedule, and 2) the ideas make up quite a few changes
to the structure of the framework and will require a substantial
deal of exploration, discussion and testing.
These two problems are hard to overcome, but we'll get there
eventually.
They both could use some work with documentation and commenting
to make them more accessable.
Well, I know this to be true for ObjcUnit at least.
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?
I do. :-)
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.