• 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
OCUnit, otest problems after Clean All
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

OCUnit, otest problems after Clean All


  • Subject: OCUnit, otest problems after Clean All
  • From: Giuseppe Alletti <email@hidden>
  • Date: Fri, 25 Feb 2005 00:07:32 +0100

Hi, I encountered an odd problem while using OCUnit.
I have a project with a test framework target that I'm using to
execute tests at build time. Everything was working fine until I made
a Clean All. That seems to have broken up otest functioning. Now every
time I try to compile the shell phase returns this:

2005-02-24 23:46:05.492 otest[4879] Usage: otest [-SenTest Self | All
| None | <TestCaseClassName/testMethodName>] <path of unit to be
tested>
2005-02-24 23:46:05.492 otest[4879] *** -[NSCFDictionary
setObject:forKey:]: attempt to insert nil value

I created a new test framework target, and it works fine. I tried to
replicate the problem (by issuing again a Clean All), but it DIDN'T
stop working... so basically I can't understand what exactly broke it
up and how to restore the old target.

Thank you,
-----------------------
Giuseppe Alletti
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: RTFD binary format internals
  • Next by Date: How to know a file is writeable?
  • Previous by thread: Re: RTFD binary format internals
  • Next by thread: How to know a file is writeable?
  • Index(es):
    • Date
    • Thread