CODEWITHSUNDEEP
iosobjective-ccocoa-touchunit-testing
Earl Grey
Earl Grey

Reputation: 7466

Unit testing private methods from a category?

I have a category on NSString class that contains a private helper method. It would be handy if I could use this method in my unit test. However I have difficulties to expose it. When I create a class extension on NSString and declare the method here, the method is not visible in unit test. And it doesn't matter if I create the class extension in a separate header file, or as a part of unit test .m file.

It looks like I am missing something here.

Any help guys?

Upvotes: 8

Views: 4195

Answers (2)

Johannes Fahrenkrug
Johannes Fahrenkrug

Reputation: 44700

You can execute any method (private or not) on an object by simply using performSelector: on it, like so:

[something performSelector:@selector(somePrivateMethod)];

But I agree with James that you should only do that when absolutely necessary.

Upvotes: 5

James Frost
James Frost

Reputation: 6990

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.

Upvotes: 15

Related Questions