• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Test failure state is highly buggy in Xcode 5
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Test failure state is highly buggy in Xcode 5


  • Subject: Re: Test failure state is highly buggy in Xcode 5
  • From: Fritz Anderson <email@hidden>
  • Date: Tue, 03 Dec 2013 10:11:01 -0600

Possibly related (see the notes, which are a bit stream-of-consciousness, but more closely related to this): rdar://problem/15417217, closed as duplicate of rdar://problem/14828018, still open.

	— F

On 3 Dec 2013, at 2:43 AM, Joar Wingfors <email@hidden> wrote:

> Hi Patrick,
>
> We'd love to take a look and try to understand what's up. Please file a bug report with a sample project or steps to reproduce. Thanks!
>
> 	<http://developer.apple.com/bugreporter/>
>
> We have fixed a lot of bugs with SenTestingKit/OCUnit in XCTest, so that may be something for you to try too.
>
> Joar
>
>
> On 2 dec 2013, at 23:57, Patrick J. Collins <email@hidden> wrote:
>
>> Hi everyone,
>>
>> I recently upgraded to XCode 5, and am finding that red "X" test failure
>> notices are incredibly buggy-- meaning, I run my tests.. I have a
>> failure..  I make the test pass, and Xcode still shows a red X,  I have
>> to quit Xcode and restart it, run the tests and then it will show that
>> it passed.  I have tried cleaning the build folder as well as the
>> target, and that makes no difference.
>>
>> Currently, I have a test failure and I simply wanted to throw in a
>> breakpoint and find out at what point there is a red X signifying
>> failure, however I can't even do this because when I run my tests, the
>> red "X" persists before the test even runs-- so there's absolutely no
>> way to trouble shoot in this way.  Quitting Xcode won't even get rid of
>> the red "X" in this case, so there's no way to start off in a clean
>> state and watch myself enter an error state.
>>
>> Has anyone else experienced this?
>>
>> I'm using 5.0.2 5A3005 with SenTest.
>>
>> Thanks.
>>
>> Patrick J. Collins
>> http://collinatorstudios.com
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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


 _______________________________________________
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


References: 
 >Test failure state is highly buggy in Xcode 5 (From: "Patrick J. Collins" <email@hidden>)
 >Re: Test failure state is highly buggy in Xcode 5 (From: Joar Wingfors <email@hidden>)

  • Prev by Date: Re: Test failure state is highly buggy in Xcode 5
  • Next by Date: XCode 5.0.2 crashes constantly
  • Previous by thread: Re: Test failure state is highly buggy in Xcode 5
  • Next by thread: XCode 5.0.2 crashes constantly
  • Index(es):
    • Date
    • Thread