iOS Automated Testing

Unit test frameworks: OCUnit, GHUnit
Functional test frameworks: UIAutomation, KIF,...

OCUnit (before XCode 5)

OCUnit: a framework developed by Sen:Te.
OCUnit has been around since 1998, when Mac OSX was still a beta operating system
OCUnit is a straightforward port of Kent Beck's SUnit framework to Objective-C
Advantage: Apple has integrated it into Xcode since Xcode 2.1
An OCUnit unit testing class contains two files: a header file with a .h extension and an implementation file with a .m extension. A newly created class’s header file looks similar to the following:

@interface QuizUnitTest : SenTestCase
@end

Writing Test Methods - An OCUnit test method has the following requirements:
- It must start with the word test. OCUnit treats methods with the test prefix as test methods and runs them automatically.
- It takes no arguments.
- It returns void.

OCUnit Assertions

STAssertEqualObjects asserts two Cocoa objects are equal.
STAssertEqual asserts two variables of a primitive data type, such as integers, are equal.
STAssertEqualsWithAccuracy asserts two floating-point variables are equal. This assertion allows you to deal with small inaccuracies in floating-point arithmetic.
STAssertFalse asserts a condition is false.
STAssertFalseNoThrow asserts a condition is false and no exceptions are thrown.
STAssertNil asserts a pointer is nil.
STAssertNoThrow asserts no exceptions are thrown.
STAssertNoThrowSpecific asserts no exceptions of a specific class are thrown.
STAssertNoThrowSpecificNamed asserts a specific exception is not thrown.
STAssertNotNil asserts a pointer is not nil.
STAssertThrows asserts an exception is thrown.
STAssertThrowsSpecific asserts an exception of a specific class is thrown.
STAssertThrowsSpecificNamed asserts a specific exception is thrown.
STAssertTrue asserts a condition is true.
STAssertTrueNoThrow asserts a condition is true and no exceptions are thrown.

Example

#import <SenTestingKit/SenTestingKit.h>

@interface QuizTests : SenTestCase

@end

@implementation QuizTests

- (void)setUp {
    [super setUp];
    // Put setup code here. This method is called before the invocation of each test method in the class.
}
- (void)tearDown {
    // Put teardown code here. This method is called after the invocation of each test method in the class.
    [super tearDown];
}
- (void)testMultiplyingTwoNegativeIntegersYieldsPositiveProduct {
  int x = -5;
  int y = -7;
  int product = x * y;
  STAssertTrue((product > 0), @"The product was less than zero.");
}

@end

Xcode 5: Unit Testing Changes

No checkbox to include a unit testing target. New Cocoa and iOS application projects automatically include a unit testing target.
Uses XCTest framework instead
OCUnit and XCTest are very similar. The biggest difference is that XCTest assertions start with XCTAssert instead of STAssert.
Xcode 5 supports both XCTest and OCUnit, but XCTest is the future of Objective-C unit testing for Mac OS X and iOS. New projects use XCTest as default.

Lab: Write Unit Tests for the Quiz programm in Lecture 13

Before Xcode 5

File -> New -> Target. Choose Cocoa Touch Unit Testing Bundle
Choose Type : OCUnit
File -> New -> File. Choose Objective-C test case class
Name the class: QuizTests, Subclass: SenTestCase

In QuizTests.m, add the following below // Put setup code here. This method is called before the invocation of each test method in the class.

Quiz *quiz = [[Quiz alloc] init];

Then add the following test method:

- (void)testNumberofQuestions
{
    int count = [quiz.questions count];
    STAssertEquals(count, 6, @"Wrong array count");
}

The test should pass.

UIAutomation

A framework for driving input to your apps
Uses UIAccessibility to identify UI elements
Scripts are written in Javascript
Tests can be run via Instruments or the Command Line

Instruments

A performance, analysis, and testing tool for dynamically tracing and profiling OS X and iOS code.
Lets you track one or more processes and examine the collected data.
Helps you understand the behavior of both user apps and the operating system.
With Instruments, you use special tools (known as instruments) to trace different aspects of a process’s behavior.
You can also use the tool to record a sequence of user interface actions and replay them, using one or more instruments to gather data.
But the GUI is hard to use, so we will use command line instead.

Automating UI Testing Using Command Line

var target = UIATarget.localTarget();
var app = target.frontMostApp();
var window = app.mainWindow();
target.logElementTree();