Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Malte Tancred <email@hidden>
- Date: Thu, 26 Jun 2003 09:11:35 +0200
Jiva DeVoe wrote:
Additionally it almost seems as if ObjCUnit is no longer being
maintained though I can't say for sure. It may be just that at the
moment ObjCUnit serves the need of every one who was maintaining it
and therefore they just haven't felt the need to release a new > version.
That's about it. :-)
(... but not entirely true. See my reply to James Quick)
However on the other hand something that is definitely very lacking in
ObjCUnit is the ability to have the line number where the failure
occurred as part of your failure Report.
...
However, with regards to ObjCUnit and printing line numbers I think
that I figured out an easy way to do this with a compiler macro.
I seldom feel the need for knowing the exact line number of
a failed assertion. My tests tend to be so small that I don't
have to know the line number. Where a failure would be ambiguos
I pass a message to the assert method as well.
OCUnit's integration with PB in this respect is quite nice though.
Good to have clickable errors that take you directly to the line
of code in question.
If this is a feature that many likes and wants we could of course
add it. Discussions on
http://oops.se/cgi-bin/wiki?ObjcUnit are
always welcome.
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.