Re: OCUnit assertion failures not showing up in text editor
Re: OCUnit assertion failures not showing up in text editor
- Subject: Re: OCUnit assertion failures not showing up in text editor
- From: Timothy Reaves <email@hidden>
- Date: Fri, 9 Oct 2009 10:59:22 -0400
On Oct 9, 2009, at 6:59 AM, Paul Hoadley wrote:
On 07/10/2009, at 9:04 PM, Paul Hoadley wrote:
I have just started using OCUnit for the first time on an existing
iPhone project. I have followed the steps for "Setting Up Logic
Testing" here:
http://developer.apple.com/IPhone/library/documentation/Xcode/Conceptual/iphone_development/135-Unit_Testing_Applications/unit_testing_applications.html
Everything is working, except that at step 8 of that section,
although I get a build failure due to the STFail(), I don't get the
error message and the red cross icon displayed in the text editor.
I get nothing in the text editor. I can drill down to find the
failure in the Build Results window, but it would be nice to get
the error message as shown in that article.
Should I be getting the in-editor messages by default? Is there
anything I can do to enable them?
I just upgraded to Xcode 3.2.1, and I still don't seem to get the
inline assertion failure messages as advertised in the article
above. I've got View > Message Bubbles > All Issues selected. Is
there anyone else using OCUnit that gets the in-editor message
bubbles?
That's a known defect.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden