One of the many new features with Xcode 7 and Swift 2 is the @testable attribute. While we have been able to do unit testing in previous versions of Xcode and Swift the big drawback has always been that any routine we wanted to test had to have an access level of public. This was a pretty big drawback especially with frameworks where we need to test routines without making them public. This has changed in Xcode 7 and Swift 2. In this post we will demonstrate how to use the new @testable attribute in our test source code to make all public and internal routines usable by our test code but not usable by other frameworks and app targets.
I would like to announce the release of RSNetworking 2 for Swift 2. RSNetworking and RSNetworking 2 are network libraries written entirely in the Swift programming language. RSNetworking 2 has all the same great features that RSNetworking has but it is written for Swift 2. This post describes RSNetworking 2 and explains how to use it.
In this post I will explain how we could use tuples to model our data and then I will show how I would replace the data model classes from my previous "Create a Data Access Layer using SQLite.swift" post with tuples. When we replace data modeling classes or structures with tuples our code can become much more compact and in some ways easier to understand however we do lose the ability to add functionality to our data model types, but is that a bad thing?