Unit test an action on UITextField - objective-c

Question

I have a simple if condition that, when met, adds a target to drop the keyboard when "Done" is tapped
- (void)addDoneWhenTrue:(UITextField *)input
{
if (YES)
{
[input addTarget:self action:#selector(textFieldFinished:) forControlEvents:UIControlEventEditingDidEndOnExit];
}
}
- (IBAction)textFieldFinished:(id)sender
{
[sender resignFirstResponder];
}
I'm using OCMock and OCUnit on iOS5. How can I create a unit test that allows me to pass in a simple UITextField input and simulate tapping the done button on it to verify that resignFirstResponder does happen (or not)?

Answer 1

You shouldn't need to mock it, and this target/action approach feels like a really roundabout way to get to what you want. As long as your controller is the UITextField's delegate, textFieldShouldReturn: will be fired when the Return (or Done in this case) key is tapped.
#pragma mark - UITextFieldDelegate
-(void)textFieldShouldReturn:(UITextField *)textField {
if (someConditionThatDeterminesWhetherKeyboardShouldCollapse) {
[textField resignFirstResponder];
}
}
Then you can test calling textFieldShouldReturn: on your controller when your condition is and isn't met. If you want, you could also make sure your view has been loaded in the test case by calling loadView, and then assert that the text field's delegate is your controller, which will ensure the view is wired up correctly.
-(void)testDoneShouldCollapseKeyboard {
[controller loadView];
expect(controller.textField.delegate).to.beIdenticalTo(controller);
id mockTextField = [OCMockObject partialMockForObject:controller.textField];
[[mockTextField expect] resignFirstResponder];
controller.someConditionThatDeterminesWhetherKeyboardShouldCollapse = YES;
[controller textFieldShouldReturn:controller.textField];
[mockTextField verify];
[[mockTextField reject] resignFirstResponder];
controller.someConditionThatDeterminesWhetherKeyboardShouldCollapse = NO;
[controller textFieldShouldReturn:controller.textField];
[mockTextField verify];
}

Answer 2

Surely you don't need to simulate clicking on a button as that's what UIKit is taking care of. You are concerned that when the textFieldFinished: method is called the right thing happens
Disclaimer
I've not used OCMock for a long time so this is an example just using the docs so it could very easily be slightly incorrect - hopefully someone can correct who has OCMock all setup.
id mock = [OCMockObject mockForClass:[UITextField class]];
[[mock expect] resignFirstResponder];
[sut textFieldFinished:mock]; // sut = system under test - taken from your screen cast ;)
[mock verify];