OCDSpec
OCDSpec copied to clipboard
paytonrules
An awesome TDD framework for Objective-C
Before, both xcodebuild and running the built product always had an exit code of 0. Now, the exit code of the xcodebuild command is 65 for spec failures and 0...
The following code: ``` ObjectiveC it(@"matches arrays", NSArray* actual = [NSArray arrayWithObjects: @"first", nil]; NSArray* expected = [NSArray arrayWithObjects: @"frist", nil]; [expect(actual) toBeEqualTo: expected]; }), ``` gives the following error...
I have a project that I wanted to run the same suite of tests against both the Mac SDK and the iOS SDK. Doing "File -> New -> New Target"...
You should really just clone the tag directly. Also warn any rvm users that they'll get a message.
The build isn't failing on failed tests anymore - I think this started when I had to use exit in main, rather than the terminateProcessWithExitCode
Tests should fail in the event of a memory leak. It should be possible to filter out certain classes sections from this check, since much of Cocoa would incorrectly report...
Probably should go ahead and write matchers like expectTrue/expectFalse for the simple data types.