Re: OCUnit vs OBJCUnit
Re: OCUnit vs OBJCUnit
- Subject: Re: OCUnit vs OBJCUnit
- From: Jiva DeVoe <email@hidden>
- Date: Wed, 25 Jun 2003 15:42:04 -0700
Both frameworks deliver that level of integration. 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.
On Wednesday, June 25, 2003, at 02:50 PM, James Quick wrote:
On Wednesday, June 25, 2003, at 04:12 PM, Jiva DeVoe wrote:
It looks like OCUnit has been receiving some updates lately, so I'm
not sure if its Project builder integration has improved. 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. If you're
interested in the macro let me know and maybe we can submit it back
to the maintainers to have it integrated into the main code.
I'm not sure what the integration used to be like, but currently, a
failed test creates a line
in the error output window, which when clicked, loads the failed test
method in the editor
window just like one would expect.
--
jiva at devoesquared.com
http://www.devoesquared.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.