Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Malte Tancred <email@hidden>
- Date: Thu, 26 Jun 2003 09:24:20 +0200
Jiva DeVoe wrote:
Specifically however I was referring to how I always disliked that
OCUnit required an external script to run the test application. Or a
least it did when I used it. There are some good reasons to do this,
in particular when writing test frameworks for things like C++, which
doesn't have reflection capabilities.
There's another reason to have an external runner. Objective C, just
like C or C++, is a language where you can mess up badly. Think
free(0x0).
One of our plans is actually to add the ability to use an external
program, much like otest in OCUnit. This runner program will never
contain tests itself but instead invoke the program created by the
test-target and interpret it's output, exit status etc. This way we
should be able to, in addition to the normal assert* failures, catch
things like crashes because of memory access violations.
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.