I created a new Cocoa Touch Static Library project with Unit Testing in XCode 4 and added a category:
// NSString+Inflections.h
@interface NSString (Inflections)
- (NSString *)pluralize;
@end
// NSString+Inflections.m
@implementation NSString (Inflections)
- (NSString *)pluralize { return self; }
@end
then added the appropriate import statement to my test cases and wrote the following test:
- (void)testPluralize
{
NSString *test = @"person";
NSString *expected = @"people";
NSString *actual = [test pluralize];
STAssertEqualObjects(actual, expected, @"Whoops");
}
However, this causes my tests to crash (not fail) with 'unrecognized selector sent to instance'.
How can I test a category inside a library?
I've compressed and uploaded the full project here if my description is inadequate.
I had the same situation when i was working in the Objective-c project. I did the following steps and it went well.
1) Select the project and goto target.
2) select Test target and add -ObjC
like showing in the image.
3) Now try to run the unit XCTest.
I was searching for an answer this problem myself and found (I believe) a simpler solution, which doesn't require remembering to add a reference in the Compile Sources list whenever a new category class is added to the project.
In the test target's build settings, add -ObjC
to the Linking / Other Linker Flags value.
Further explanation for why this error actually happens can be found at Apple Reference.
Edit: Be sure to see this answer about unit test not finding files
+1 For uploading the project. The problem is your test target does not include NSString+Inflections.m in the Build Phases.
In XCode 4
You should then get something similar the following output
TestSuite '/blahblah/PoppyTests.octest(Tests)' finished at 2011-03-28 21:31:34 +0000. Executed 1 test, with 1 failure (0 unexpected) in 0.000 (0.002) seconds
I can also confirm that adding the required files to the Test project's Build Phases > Compile Sources collection solves this problem. Thanks a bunch!
When I tried the -all_load approach, however, I started to receive a bunch of errors, like that _CGSizeZero is undefined for architecture i386. It turns out that some code - like this one, where I use CGSizeZero in one of my classes - can make the second approach break.
Once I replaced CGSizeZero with CGSizeMake(0, 0), however, the second approach worked great as well.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With