はてなブックマーク

First, let me point out the conference’s logo/mascot. The Swift bird has never been so adorable! Without a doubt, this is the cutest tech conference logo I’ve ever seen. Talks The conference spans 2 days, in a single-track format. Talks are limited to 20 minutes, so things keep moving along quickly. (As a speaker, it was a nice challenge to have to condense my thoughts into a 20-minute talk.) Almo

And here is sample code. Build SwiftMocks.xcworkspace and run the tests. Experiment with changing things in Waiter.swift to see how the tests report those changes. The official repository of Swift Hamcrest is here. Recommended BookDisclosure: The book link below is an affiliate link. If you buy anything, I earn a commission, at no extra cost to you. Refactoring: The Improving the Design of Existin

I sometimes talk to myself. Our classes often do. But there are a couple of places where doing so is risky in Objective-C: init and dealloc. This post is part of the Code Smells in Objective-C series. Here’s something I see a fair bit in code for Objective-C init and dealloc. I’ll give a simple example. Can you tell what’s wrong? - (id)initWithFoo:(id)foo { self = [super init]; if (self) self.some

With few exceptions, using Xcode preprocessor macros is a code smell. C++ programmers have had this beat into them: “Don’t use the preprocessor to do something the language itself provides.” Unfortunately, more than a few Objective-C programmers have yet to get that message. This post is part of the Code Smells in Objective-C series. Here’s a handy command to run from Terminal. It examines source

One of the first things I do when working on any Xcode project is set up code coverage. If the coverage shows a hole, I know that area is lacking unit tests. (Be careful, the opposite isn’t true: Just because some code has been touched by unit test execution doesn’t mean it’s actually covered. If altering the behavior of the code causes a test to fail, then you know it’s covered.) Many people use 

Test-driven development (TDD) is a series of small steps. It can be difficult to grasp until you see those steps demonstrated. That’s why I made this screencast. It was sparked by a Stack Overflow question that said, “All the examples of unit testing I read about seem to be extremely simple and trivial.” The question asks how to write unit tests for a piece of sample code that uses NSUserDefaults.