Re: Unit Tests Always Succeeding (And Not in the Good Way)
Re: Unit Tests Always Succeeding (And Not in the Good Way)
- Subject: Re: Unit Tests Always Succeeding (And Not in the Good Way)
- From: Jeff Kelley <email@hidden>
- Date: Wed, 05 Sep 2012 21:36:45 -0400
Switching to GDB did in fact fix it for me. Thanks for the tip.
For those interested, I posted rdar://12242936 about it (OpenRadar: http://openradar.appspot.com/radar?id=1922406).
Jeff Kelley
On Sep 5, 2012, at 9:30 PM, Shazron Abdullah <email@hidden> wrote:
> Try switching to GDB. See: http://stackoverflow.com/a/9882128/219684
>
> On 2012-09-05, at 5:53 PM, Jeff Kelley <email@hidden> wrote:
>
>> Hello all,
>>
>> My apologies if this has been discussed before—I searched my archives, but it’s possible I missed something. I’m using Xcode 4.4.1 on OS X 10.8.1, and I can’t get unit tests to fail when trying to test my iOS static library project. Even with the stock template test that looks like so:
>>
>>> - (void)testExample
>>> {
>>> STFail(@"Unit tests are not implemented yet in AmazeKitTests");
>>> }
>>
>> Every time I hit ⌘U to test, the “Test Succeeded” pop-up appears, though the failure is marked in Xcode’s Issue Navigator. I can reproduce this by creating a new static library project in Xcode with tests and hitting ⌘U. Is anyone else seeing this? I’ll submit a Radar after this e-mail either way, but if anyone has a workaround that would be spectacular.
>>
>> Jeff Kelley
_______________________________________________
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