Scribd
Upload
177 views124 pages

iOS CI Tips for Developers

Here are a few tips for deploying your iOS app from a continuous integration build: 1. Use TestFlight or HockeyApp for over-the-air distribution to testers. Both have Jenkins plugins that make it easy to automatically upload your signed IPA file from a build. 2. Store sensitive credentials like API keys out of your scripts, either as environment variables or global properties in Jenkins. 3. Create different "build configurations" in Jenkins - e.g. nightly, beta, release. Trigger different deployment steps based on the config. 4. Consider deploying to both the App Store and internal testers in parallel. This allows testing the App Store submission process without disrupting your main

Uploaded by

Kevin Munc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
177 views124 pages

iOS CI Tips for Developers

Here are a few tips for deploying your iOS app from a continuous integration build: 1. Use TestFlight or HockeyApp for over-the-air distribution to testers. Both have Jenkins plugins that make it easy to automatically upload your signed IPA file from a build. 2. Store sensitive credentials like API keys out of your scripts, either as environment variables or global properties in Jenkins. 3. Create different "build configurations" in Jenkins - e.g. nightly, beta, release. Trigger different deployment steps based on the config. 4. Consider deploying to both the App Store and internal testers in parallel. This allows testing the App Store submission process without disrupting your main

Uploaded by

Kevin Munc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

CI for iOS:

do more while you sleep


Kevin Munc – @muncman
Method Up LLC
[MU]
CI?
For iOS?
Pain
Pain & Suffering
It can be done

• Start with the basics


• Xcode and the command line
• Version control and CI server
• Script it, run it, schedule it
Tip #1
Jenkins

• [Link]
• Mac installer or via homebrew
• Many alternatives
• Many plugins
Tip #1.1
How many Simulators does
it take to break a build?
A CI server gives you:
A CI server gives you:

Automation
A CI server gives you:

Automation

Feedback
A CI server gives you:

!
Automation
f u l
de r
on
W
Feedback
A CI server gives you:

!
Automation i n d
f u l f m p s)
de r c e o n a
n a e r
Wo Pe bett
Feedback (fo r
Requirement: OS X
Requirement: OS X
• [Link]

• [Link]

• [Link]

• [Link]

• [Link]

• [Link]

• [Link]
Requirement: OS X
• [Link]

• [Link]
h t ,
n i g
• [Link]
C I t o r u n a
ac
t
,
u l e M
• [Link]
O r sch e d
o u
on y you slee
r o w n
p . . .
• [Link] w h i l e

• [Link]

• [Link]
Security
sudo /usr/sbin/DevToolsSecurity --enable
Security

sudo xcodebuild -license


Credentials
• The CI server needs access to your
repository
• SSH key
• The CI server needs Keychain credentials if
you want to sign your builds
• Developer certificate and profiles
Keychain
• Export and Import using Keychain Access app
• Keys and Certificates
• Or use the command line:
• sudo security import /path/to/[Link] -k /Library/Keychains/
[Link]

• sudo security import /path/to/distribution.p12 -k /Library/Keychains/


[Link]

• Don’t forget about provisioning profiles


• Troubleshooting: [Link]
Tip #2
Avoid this error
from Xcode
RunPlatformUnitTests:
warning: Skipping tests;
the iPhoneSimulator platform does
not currently support application-
hosted tests (TEST_HOST set).
The culprit

/Applications/[Link]/
Contents/Developer/
Platforms/
[Link]/
Developer/Tools/
RunPlatformUnitTests
The workaround(s)
Xcode Plugin

• [Link]

• Specify provisioning profile


• Keychain access
• Signed IPA
Xcode Plugin

• Recommended xcodebuild arguments:


• GCC_SYMBOLS_PRIVATE_EXTERN=NO
• COPY_PHASE_STRIP=NO
• Allows test bundle to link with Release
build symbols
Signing with the Plugin
Signing with the Plugin
Signing with the Plugin
Tip #3
Prefer Scripts
over CI Plugins
• More flexibility
• More resilient to Apple’s changes
• More power to adapt and expand (specificity)
• Less coupling to the specific CI server type
• You can version control the settings easier
xcodebuild

xcodebuild \
clean build
Tip #4
Be specific with
xcodebuild options
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
xcodebuild
xcodebuild \
-scheme SOLID \
-target SOLID \
-configuration Debug \
-arch i386 \
-sdk iphonesimulator \
clean build
Tip #5
Specify Alternate
Output Locations

• Don’t rely on Xcode’s cryptic locations


• This will make your scripts easier to
manage
# Build location for Instruments test runs.
CI_BUILD_DIR=/tmp/SOLID_AUTOMATION
mkdir -p $CI_BUILD_DIR

xcodebuild \

... \

CONFIGURATION_BUILD_DIR=$CI_BUILD_DIR \

clean build
# Build location for Instruments test runs.
CI_BUILD_DIR=/tmp/SOLID_AUTOMATION
mkdir -p $CI_BUILD_DIR

xcodebuild \

... \

CONFIGURATION_BUILD_DIR=$CI_BUILD_DIR \

clean build
# Build location for CI test runs.
CI_BUILD_DIR=/tmp/SOLID_AUTOMATION
mkdir -p $CI_BUILD_DIR

xcodebuild \

... \

CONFIGURATION_BUILD_DIR=$CI_BUILD_DIR \

clean build
Demo
Tip #6
Ensure Return Codes

• If the tool you are invoking in your script


doesn’t return an exit code indicating
pass/fail, it’s up to you.
• Unix-friendly 0 (success) or 1 (failure)
Tip #7
Test against multiple
SDKs

-sdk iphonesimulator5.0
-sdk iphonesimulator5.1
-sdk iphonesimulator6.0
Other Tools
to Know About
• xcode-select (manage xcode path)
• Overridden by DEVELOPER_DIR

• xcrun (find and run dev tools)


• ibtool (for Interface Builder files)
• /Applications/[Link]/Contents/Developer/usr/bin/

• Variables in Xcode
• “Build Settings Reference”
OCUnit
Other Related Tools
Other Related Tools
• OCMock • XcodeTest
• OCMockito • AutoBuild
• OCHamcrest • xcodeproj (CocoaPods)
• Expecta • Circle?
• TinyMock • Simon?
• LRMocky • ios-maven-plugin
• OCUnit2JUnit • Ceedling
• OCUnitReport • XcodeCoverage
• Kicker • JMRTestTools
• xcodebuild-rb • Nocilla
• xcodearchive • OHHTTPStubs
OCUnit Alternatives
• Kiwi
• Cedar
• OCDSpec
• C++ Automated Test Cases in Headers
(CATCH)
• Objective-Shoulda
• Specta
Tip #8
OCUnit2JUnit for
Test Results

• [Link]
• [Link]
• Converts output to JUnit format for easier
transformation to HTML
UIAutomation
Other UIAutomation
Tools
• tunup_js • ios-sim

• jasmine-iphone • ios-sim-locale

• uiautomation-jasmine- • iphonesim
iphone
• ui-auto-monkey
• Bwoken
• ui-screen-shooter
• Zucchini Framework
• uiautomation-rb?
• WaxSim
UIAutomation
Alternatives
• Frank • Objective C Slim
(ocslim)
• (iCuke)
• AutomationKit
• KIF
• Sikuli
• Calabash
• MonkeyTalk (formerly
• UISpec FoneMonkey)

• Bromine • Plus other commercial


tools, such as Telerik Test
Studio for iOS
Tip #9
PListBuddy
is Your Buddy

/usr/libexec/PlistBuddy
Tip #10
Always quit the
simulator
• killall
• killall -m -KILL "iPhone Simulator"
• AppleScript
• osascript -e 'tell app "iPhone Simulator"
to quit'
Tip #11
Use Jonathan Penn’s
AutomationExample

[Link]
Demo
More?
Code Coverage

“Risk coverage”
Coverage Tools
• gcov
• GCC’s coverage tool
• GUIs for gcov
• LCOV (HTML)
• CoverStory (Mac app)
• ocov?
Tip #12
gcovr for
Coverage Automation

Produces Cobertura-formatted output


from gcov data
Tip #12.1
Enable Test Coverage
Static Analysis

• Clang
• [Link]
• scan-build
Tip #13
Symbolic links
can be your ally
Avoid scan-build Pain
sudo ln -s \
/Applications/[Link]/Contents/Developer/Toolchains/
[Link]/usr/lib/arc/
libarclite_iphonesimulator.a \
/usr/lib/arc/libarclite_iphonesimulator.a
What about
test build deployment?
Tip #14
Use TestFlight

• [Link]
• OTA deployment
• SDK for more features
• Free!!
TestFlight

• Web UI
• Desktop App
• REST API
• Jenkins Plugin
TestFlight Alternatives
• HockeyApp
• [Link]

• Also has a Jenkins plugin (forked)

• BetaBuilder for iOS


• [Link]

• More players in this space, esp. for enterprises...


TestFlight Config

• API Token and Team Token


• Need a signed IPA
• They get an email with a link for OTA
installation!
Tip #15
Protect Your Tokens
• API Token & Team Token
• Keep them out of scripts
• Instead, define them in Jenkins (and leverage
Jenkins security)

• 'Configure System'
• 'Global properties' section

• Or use the plugin (same parameters)


TestFlight Plugin
TestFlight Script
Deployment
Deployment
Q: Once you have a nightly job to build,
unit test, sign an IPA and deploy it to QA,
what’s next?
Q: Once you have a nightly job to build,
unit test, sign an IPA and deploy it to QA,
what’s next?

A: Sleeping easy.
Documentation

• Appledoc
• Doxygen
• HeaderDoc
DocSets
Appledoc
Doxygen
Tip #16
Don’t stop there!
Other Goodies
Other Goodies
• Ensure your site or API is up
• Scan your code for TODOs and FIXMEs
• Get trend reports for lines of code
(SLOCCount w/ sloc2html)
• Scan for duplicated blocks of code (CPD,
Simian, etc.)
• Use agvtool (Apple-Generic Versioning
Tool) to increment your build number
Still Missing
• Cyclomatic Complexity

• Coding convention/Style checker

• Code Formatter

• Uncrustify, UniversalIndentGUI

• UML Generation

• via CLI, as opposed to OmniGraffle (AppleScript?)

• ER Diagram from Core Data schema


Tip #n
Sources
• Slides: [Link]

• [Link]

• [Link]

• [Link]

• [Link]
• [Link]
tests-from-the-command-line-in-ios/

• [Link]

• et cetera
Thank you!
• CodeMash organizers
• CodeMash sponsors
• and YOU!

[MU]
Thank you!
• CodeMash organizers
• CodeMash sponsors
• and YOU!
Questions?
[MU]

You might also like