Upgrading to Xcode 3.1 solved the problem.

On Aug 15, 2008, at 1:01 PM, Nick Pilch wrote:
Hi. I'm trying to put the infrastructure into my project for running unit tests and I'm stuck. The tests don't seem to execute. I've set things up as described here for independent tests: http://developer.apple.com/documentation/DeveloperTools/Conceptual/UnitTesting/Articles/CreatingTests.html
When trying to build/run this test I get:

arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable

Here's my test method:

- (void) testTest
{
        STAssertEquals(0, 1, @"Dude, 0 is not 1", nil);
}

Any help? Thanks.

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/npilch%40tacitknowledge.com

This email sent to [EMAIL PROTECTED]

------------------------------------------------

Nick Pilch / Tacit Knowledge, LLC
[EMAIL PROTECTED]
Cell: 510-381-6777



_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to