• 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: TDD : Prior test failures in Issues Navigator are annoying
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TDD : Prior test failures in Issues Navigator are annoying


  • Subject: Re: TDD : Prior test failures in Issues Navigator are annoying
  • From: Alex Zavatone <email@hidden>
  • Date: Tue, 09 Jul 2013 17:28:48 -0400

Well, I meant to do a clean before a build, but I see in your link that doesn't work.

On Jul 9, 2013, at 12:53 PM, Jerry Krinock wrote:

>
> On 2013 Jul 09, at 07:38, Alex Zavatone <email@hidden> wrote:
>
>> Does a clean before building help?  Command Shift K.
>
> Thank you, Alex.  I'm not sure what you mean by "before building", but no ⇧⌘K does not clear the issues.
>
> Something really strange just happened.  After a while, the test failures disappeared from the Issues Navigator.  After rewriting some code, I re-tested, ⌘U, a few times and now issues are showing only in the Log and not in the Issues Navigator.  Then, as I was typing this message, out of the corner of my eye I saw something change in the partially-obscured Issues Navigator of the Xcode window.  Poof!  Test failures are back in!  This was about two minutes *after* the test had completed.  There is no text in the filter field at the bottom of the Issues Navigator.

That's crazy.  Are the test failures written to a log file or are the errors stored in a datastore and are occasionally synced to the display?

This reminds me about what I did when I was pissed off that the console was microscopic and it's stupidly difficult to simply open an additional window that only contains the console.  I extended NSLog and made sure that every NSLog wrote out all the messages to a file I could tail in the terminal.  This way, I can open the terminal on another monitor - or even other computer - and get my readout of what I wanted to output, without having to fight Xcode and the unpleasant "one window to rule them all" approach.

Maybe that's an option.



 _______________________________________________
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


  • Follow-Ups:
    • Re: TDD : Prior test failures in Issues Navigator are annoying
      • From: Jerry Krinock <email@hidden>
References: 
 >TDD : Prior test failures in Issues Navigator are annoying (From: Jerry Krinock <email@hidden>)
 >Re: TDD : Prior test failures in Issues Navigator are annoying (From: Alex Zavatone <email@hidden>)
 >Re: TDD : Prior test failures in Issues Navigator are annoying (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Launch Services Issue/Question - two apps using same file extensions
  • Next by Date: Re: Type of @true in Obj-C vs Obj-C++
  • Previous by thread: Re: TDD : Prior test failures in Issues Navigator are annoying
  • Next by thread: Re: TDD : Prior test failures in Issues Navigator are annoying
  • Index(es):
    • Date
    • Thread