iPhone Application Testing

iPhone Application Testing
Testing apps in the real world

iPhone App Testing - Copyright 2010 Element 84, LLC

Thursday, June 2, 2011

Who am I?

Dan Pilone (dan@element84.com, @danpilone)
Author of Head First Software Development and
Head First iPhone and iPad Development
Developed software for NASA, Raytheon, UPS,
Hughes, and the Naval Research Laboratory
Founder of Element 84, LLC



Standard iPhone Testing



Automated Testing



Why automate your tests?



Verify your code does what
you think.



Keeps your code doing it...



Gives you license to make
changes



Basic Unit Testing

Support is built into Xcode
Called Logic Tests by Apple
Run as part of your build process
Small scope for testing



Setting up Logic Tests



Add a Unit Test Bundle



Add a Test Case



nts
E ach class represe
a test suite
@implementation LogicTests

- (void) testFail {
! STFail(@”This’ll never work.”);
a
Each method represents start }
specific test and should
with “test”. ber of
@end There are a numrify code.
assertions to ve



Demo*

* Xcode 3.2.4 requires a workaround source ﬁle



ST* Macro Sample

STAssertTrue STAssertEqualObjects

STAssertFalse STAssertEquals

STAssertThrows STAssertNotNil



Notes...

Run at build time and not easily debuggable
Don’t run in the real context of the app
Can’t run on a real device
Fully automatable in a CI environment



Test Driven
Development Requirements
Design Code Test (what’s done)

An iteration contains all the
stages of a complete process.

Somewhat of a misnomer
Largely a design process
Red, Green, Refactor...



Test Driven Development works on a very simple cycle:

First you write a test that checks whatever functionality you’re about to
write. Obviously it fails, since you haven’t implemented the functionality
yet. This is the red stage, since your test GUI probably shows the test
in red (failing).

Next, implement the functionality to get that test to pass. That’s it. No
more. Nothing fancy. Write the simplest code you can to get your test
to pass. This is the green stage.

Finally, after your test passes, you can go back in and clean up some
things that you may have noticed while implementing your code. This
is the refactor stage. In the example for Starbuzz, you don’t have any
other code to refactor, so you can go right on to the next test.



Demo



Application Level Testing

Test at the Integration Test Level
Run on a physical device
Build on what you know about unit testing



Duplicate your app target



Add an App Test Bundle



Add the tests to the target



Add the test bundle



- (void) setUp {
! appDelegate = [[UIApplication sharedApplication] delegate];
! viewController = appDelegate.rootViewController;
! rootView = viewController.view;
}

- (void) testAppDelegate {
STAssertNotNil(appDelegate, @"App delegate is nil!");
}



Notes...

Only run on the device
Can tempt you to expose things publicly that might be
best left private
Let you perform full integration and load testing



Full Application Testing



UIAutomation Testing

JavaScript based testing using UIAutomation
framework
Leverages iPhone accessibility to let you automate your
application in the simulator
Runs inside Instruments to support proﬁling
Full support for logging, screen captures, gestures,
orientation and multitasking



Notes...

Use tune_up.js
Provides a nice assertion and test wrapper around
UIAutomation
http://github.com/alexvollmer/tuneup_js
Must run in Instruments making it difﬁcult to use in a CI
environment



Sample test

test("Basic List", function(target, app) {
! UIALogger.logMessage("Checking initial row count…");
!
! mainWindow = app.mainWindow();
! var topicTable = mainWindow.tableViews()[0];
! var initialCount = topicTable.cells().length;
! assertEquals(21, initialCount);
});



Run UIAutomation in Instruments



More UIAutomation
information

Session 306 from WWDC 2010 Videos
https://developer.apple.com/wwdc/iphone/library/
documentation/DeveloperTools/Reference/
UIAutomationRef/index.html



iCuke

iPhone App integration testing with Cucumber
Includes basic set of steps for interacting with your app
in the simulator
Let’s you execute and test “app requirements”
Not quite 100% there...
Available here: http://github.com/unboxed/icuke



Automate TDD and BDD



CI with iPhone Apps

Deﬁnitely achievable!
Requires some setup due to code signing
Uses xcodebuild to build your project just like Xcode
Take advantage of tools like scan-build (Clang) and
gcovr to generate static analysis and Cobertura reports
Use ocunit2junit.rb to generate test reports



Questions?

Dan Pilone
@danpilone
dan@element84.com

iPhone Application Testing

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (11)

Último

Último (20)

iPhone Application Testing