[Solved] Re: Trust, but verify - OCUnit testing of Target-Action Connections
[Solved] Re: Trust, but verify - OCUnit testing of Target-Action Connections
- Subject: [Solved] Re: Trust, but verify - OCUnit testing of Target-Action Connections
- From: "David H. Silber" <email@hidden>
- Date: Wed, 21 Jan 2009 23:59:29 -0500
On Mon, Jan 12, 2009 at 04:03:10PM -0500, David H. Silber wrote:
> 1) Is there not any way to test the connections set up in the nib
> owned by the application? In particular, the menus.
> As things stand, I still end up with a bunch of untestable code.
I was able to test the connections set up in the application's nib file
by ditching the idea that they needed to be tested via OCUnit. Instead,
I used NSAssert from within the application, making sure that the test
code is enabled only when the application is compiled with the Debug
configuration.
It may not sound like a big deal, but it was not obvious when I started
how this was to be accomplished.
This works, but it seems a bit clunky to me. If anyone can suggest a
better way to do this, I would be interested.
Thanks,
David
P.S. One thing I still don't understand is that the title of the
application menu displays correctly, but internally has the value
@"Apple". Can anyone explain this?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden