• 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 Frameworks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unit Testing Frameworks


  • Subject: Re: Unit Testing Frameworks
  • From: Thaddeus Cooper <email@hidden>
  • Date: Sun, 7 Dec 2008 20:11:07 -0800

Thanks. I finally got over the hump -- it turned out to be that the test cases were not in the right target.

Now that that's fixed I'm trying to get debugging of the framework working and I keep getting a launch path not accessible error. I added the executable target and set the arguments to

-SenTest All
Section Tests.octest

and my environment variables to:

DYLD_LIBRARY_PATH $(BUILT_PRODUCTS_DIR)
DYLD_FRAMEWORK_PATH $(BUILT_PRODUCTS_DIR)
OBJC_DISABLE_GC YES

otest runs but gives the following error:

objc[46258]: GC: forcing GC OFF because OBJC_DISABLE_GC is set
Running…
objc[46258]: GC: forcing GC OFF because OBJC_DISABLE_GC is set
2008-12-07 20:03:03.415 otest[46258:813] Usage: otest [-SenTest Self | All | None | <TestCaseClassName/testMethodName>] <path of unit to be tested>
2008-12-07 20:03:03.421 otest[46258:813] launch path not accessible


I've tried -SenTest All, -SenTest None, and a variety of things for Section Tests.octest including prefixing it with ${BUILT_PRODUCTS_DIR} and without, and even removing it altogether. All with the same result. I'm pretty sure that the problem is a dumb one but I can't see it.

Once again -- thanks to all who have responded and if anyone has any thoughts I'd be really appreciative.

Thanks very much.

Thaddeus O. Cooper
(email@hidden)



On Dec 7, 2008, at 4:48 PM, Rob Keniger wrote:


On 08/12/2008, at 8:25 AM, Thaddeus Cooper wrote:
The framework builds correctly -- no warnings or errors, but the test cases do not get built automatically. I then switch my active target to my test bundle (creatively named Tests), and do a build and get the following error dump (note I've highlighted the line I believe to be the major error):


2008-12-07 14:15:35.042 otest[42098:80f] The executable for the test bundle at /Users/cooper/src/Sections/build/Debug/Tests.octest could not be found.


It looks like you have not configured the BUNDLE_LOADER configuration directive in your Tests target's settings to point to your executable.

You need to make sure that the bundle loader is set to $ {BUILT_PRODUCTS_DIR}/YourAppName.app/Contents/MacOS/YourAppName for the test target to be able to launch your app and run the tests.

--
Rob Keniger



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Unit Testing Frameworks
      • From: Chris Hanson <email@hidden>
References: 
 >Unit Testing Frameworks (From: Thaddeus Cooper <email@hidden>)
 >Re: Unit Testing Frameworks (From: Rob Keniger <email@hidden>)

  • Prev by Date: Encrypted web services connections and pk12 certificates
  • Next by Date: Re: Child Window issues
  • Previous by thread: Re: Unit Testing Frameworks
  • Next by thread: Re: Unit Testing Frameworks
  • Index(es):
    • Date
    • Thread