• 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: otest -- only useful for bundles?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: otest -- only useful for bundles?


  • Subject: Re: otest -- only useful for bundles?
  • From: Chris Hanson <email@hidden>
  • Date: Tue, 22 Nov 2005 14:16:38 -0800

On Nov 22, 2005, at 8:41 AM, James Bucanek wrote:

So the only time a program of any kind needs to contain custom code to support unit testing is in the case of a C/C++ tool where there is no convienient way for a static initializer in the unit test bundle to intercept its normal execution?

Yes, exactly.

  -- Chris

_______________________________________________
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: 
 >Re: otest -- only useful for bundles? (From: James Bucanek <email@hidden>)

  • Prev by Date: Re: otest -- only useful for bundles?
  • Next by Date: Changing automatic header insert
  • Previous by thread: Re: otest -- only useful for bundles?
  • Next by thread: Re: otest -- only useful for bundles?
  • Index(es):
    • Date
    • Thread