• 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: Unit testing - printf and gdb
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unit testing - printf and gdb


  • Subject: Re: Unit testing - printf and gdb
  • From: Aaron Montgomery <email@hidden>
  • Date: Tue, 10 Jun 2008 06:42:38 -0700


On Jun 10, 2008, at 2:29 AM, Alan Shouls wrote:

I have been experimenting with the C++ unit testing that is built into xcode. It is pretty straightforward and works just fine. In test driven development you fully expect to get test failures - which you then debug and fix. And here is my problem

- If I include printf or squirt stuff in cout, when running the tests in xcode, I can't seem to see any output - where does it go? I have optimistically looked at the console in xcode, and in the proper console and can't seem to see anything. My guess is that this is some basic "numpty" error on my part - but I would be happy for a heads up.

I think calls to cout from the unit tests place the messages in the build transcript. Have you looked there?


Aaron
_______________________________________________
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: Unit testing - printf and gdb
      • From: Alan Shouls <email@hidden>
References: 
 >Unit testing - printf and gdb (From: Alan Shouls <email@hidden>)

  • Prev by Date: Re: Unit testing - printf and gdb
  • Next by Date: Re: Unit testing - printf and gdb
  • Previous by thread: Re: Unit testing - printf and gdb
  • Next by thread: Re: Unit testing - printf and gdb
  • Index(es):
    • Date
    • Thread