I would look in the test phase of the scheme editor for your framework scheme
you want to test.
What you will be looking for when you click on test in Test (I know it is
confusing) and then in the info panel look to see what test targets are
included in the lists titled tests. If you have no
calhost:10355/_utils>. on your server machine, as pointed out on
> one of Honza's pages.
>
>
>
>
> On Jan 11, 2016, at 3:30 AM, Kevin Meaney wrote:
>
>> Hi Alex,
>>
>> I would also like this information amongst plenty of other info.
>>
>>
When my OS X Application fails to be UI tested I have lots of the following
messages in the Servers console application. Also when I look at the
Screenshots taken I get in the middle of the screen shot the following dialog
displayed. Looking at the output it looks like xcscontrol restarts the
Hi Alex,
I would also like this information amongst plenty of other info.
Are you doing OS X development, are you trying to do UI testing with continuous
integration?
If you find any information I’d love to know.
I’ve found Honza Dvorsky’s website useful
integration that I do not see when I run the tests locally. I
have no idea if this information is even available but I’d really like to have
access to more information than is shown in Xcode but I this information does
not appear to be available.
Kevin
> On 11 Jan 2016, at 08:30, Kevin Meaney
Oh boy. Glad to hear you have mostly reached the other side. I on the other
hand am still in the is this ever going to work stage.
Your comment about the age of various documents rings so true with not enough
knowledge to assess when the information might actually be counterproductive.
To add a breakpoint on malloc_error_break do command 7 which shows the break
points in the navigator view. At the bottom of the view is a plus button. Click
the button. Then select Add Symbolic Breakpoint... From the menu.
Enter malloc_error_break in the symbol text field and hit return.
Done.
