• Setting up and executing automated unit tests is slightly more involved than generating built apps for distribution.
• The following is the set up that I use for some of my projects, I have just renamed the project to TestProject for convenience.
• For this article I am assuming that you have Jenkins, Xcode, Xcode Command Line Tools, and the Xcode Jenkins plugin already installed.
• Because I use cocoaPods for dependency management, I build a workspace using custom build schemes. To build a single project with a unit-test target would make these steps easier.

We will have a look at a TestProject to get an idea of how jenkins can be used to build, sign and deploy iOS projects. The whole process consists of 4 steps. Note that to deploy an app in this manner, an enterprise distribution certificate is required for each app. This guide is how I have set up my enterprise builds for my apps that use cocoaPods for dependencies, but most of the same principles apply for any iOS apps. Because the project uses cocoaPods, it means we have to build a workspace and have a build scheme set up.

This is the style guide that I follow when programming in Objective-C, this is for my own reference, but other people may find this useful.

It is pretty rare to actually have to dive into the objc-runtime for any day to day coding. Most developers wont have to touch the runtime, however it is helpful to know what is possible and be able to use it if required. The objective-c runtime is written in C and is how the underlying parts of the objective-c language work including message sending, ivars and properties. This post shows an example of where I have used the Objective-C runtime in one of my projects.

This is a list of git notes that I use everyday. Hopefully someone else finds it useful. I will update this list over time.