Common unit testing guidance would tell you not to try and test your private methods. Only test via your public interfaces. Private methods are simply an implementation detail that could change at any time, when you refactor. Your public interfaces should be pretty stable, and will exercise your private methods.
However, if you still want to test your private category methods, the following works for me...
First, your category:
UIImage+Example.h
@interface UIImage (Example)
@end
UIImage+Example.m
@implementation UIImage (Example)
+ (NSString *)examplePrivateMethod
{
return @"Testing";
}
@end
MyExampleTests.m
#import <XCTest/XCTest.h>
#import "UIImage+Example.h"
@interface UIImage (Example_Test)
+ (NSString *)examplePrivateMethod;
@end
@interface MyExampleTests : XCTestCase
@end
@implementation MyExampleTests
- (void)testExample
{
XCTAssertEqualObjects(@"Test", [UIImage examplePrivateMethod], @"Test should be test");
}
@end
Essentially, redeclare your private method in a new category in your test. However, as mentioned above this is exposing private methods just for the purpose of testing, and coupling your tests to your implementation.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…